On Mon, 28 Mar 2005 20:25:00 -0500, Daniel Berlin <[EMAIL PROTECTED]> wrote:
> On Mon, 2005-03-28 at 14:27 -0800, Mike Stump wrote:
> > On Mar 28, 2005, at 12:12 PM, Christian Joensson wrote:
> > > Aurora SPARC Linux release 2.0 (Kashmir FC3) UltraSparc IIi (Sabre)
> > > sun4u:
> >
> > > I get these failures and just would like to ping for any ideas what
> > > might be wrong...
> > >
> > > FAIL: gcc.dg/pch/static-1.c -O0 -g assembly comparison
> > > FAIL: gcc.dg/pch/static-1.c  -O0  assembly comparison
> > > FAIL: gcc.dg/pch/static-1.c  -O1  assembly comparison
> > > FAIL: gcc.dg/pch/static-2.c -O0 -g assembly comparison
> > > FAIL: gcc.dg/pch/static-2.c  -O0  assembly comparison
> > > FAIL: gcc.dg/pch/static-2.c  -O1  assembly comparison
> > > FAIL: gcc.dg/pch/static-3.c -O0 -g assembly comparison
> > > FAIL: gcc.dg/pch/static-3.c  -O0  assembly comparison
> > > FAIL: gcc.dg/pch/static-3.c  -O1  assembly comparison
> >
> > http://gcc.gnu.org/ml/gcc-regression/2005-03/msg00025.html
> >
> > http://gcc.gnu.org/ml/gcc-regression/2005-03/msg00127.html
> >
> >
> 
> Doubtful it's directly related.
> He's getting miscompares without -g, and his compiler is newer than my
> patch.  If it was really the same problem,
> 1. it would have either gone away or showed up with each patch
> 2. it would have only affected -g
> 3. it would have affected gcc.dg/pch/save-temps.c
> 

This is now http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20673

-- 
Cheers,

/ChJ

Reply via email to