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 maint
On Sun, Mar 27, 2005 at 01:07:09PM -0800, Mike Stump wrote:
> On Sunday, March 27, 2005, at 11:58 AM, Per Bothner wrote:
> >Now I'm willing to fix those tests by adding -fno-show-column where
> >necessary
>
> Ick. I favor adding it unconditionally to compile lines over this.
> See -fmessage-le
On Sunday, March 27, 2005, at 11:58 AM, Per Bothner wrote:
Now I'm willing to fix those tests by adding -fno-show-column where
necessary
Ick. I favor adding it unconditionally to compile lines over this.
See -fmessage-length code (gcc/testsuite/lib/g++.exp) for hints. And
even that, I'm not s
On Sunday, March 27, 2005, at 11:58 AM, Per Bothner wrote:
If you run 'make check' after --enable-mapped-location (even
just --enable-languages=c) you'll find some apparant regressions.
They aren't real regressions - it's just now we now get column numbers
in some of the diagnostic messages, and t
If you run 'make check' after --enable-mapped-location (even
just --enable-languages=c) you'll find some apparant regressions.
They aren't real regressions - it's just now we now get column numbers
in some of the diagnostic messages, and this confuses dejagnu.
Now I'm willing to fix those tests by
