On Mon, 28 Mar 2005, Janis Johnson wrote: > There are several workarounds in the GCC testsuite for things that could > be better handled in DejaGnu if the next release of GCC could require a > new DejaGnu version. That might be the right thing to do for GCC 4.1. > Ben Elliston is the DejaGnu maintainer; he's expressed interest in the > past in modifying DejaGnu to support GCC's needs.
I'm one of those who haven't been too happy about requiring new versions of tools required for testing GCC (not the least because I've been using several systems where I just had limited access). However, if we can reap real benefits from requiring a newer version of DejaGnu and have a bit of a lead time (i.e., the new DejaGnu version is released a few months before GCC 4.1), relying on such a new version does sound like an okay plan. Gerald
