Re: other/8948: [3.3 regression] Definition of __i686 causes big Problems

Re: other/8948: [3.3 regression] Definition of __i686 causes big Problems

[jbuck]

Synopsis: [3.3 regression] Definition of __i686 causes big Problems

State-Changed-From-To: analyzed->closed
State-Changed-By: jbuck
State-Changed-When: Tue Feb 11 00:21:58 2003
State-Changed-Why:
    This is not a gcc bug.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8948

Re: other/8948: [3.3 regression] Definition of __i686 causes big Problems

[Volker Reichelt]

The following reply was made to PR other/8948; it has been noted by GNATS.

From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: jbuck@synopsys.com
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, norbert_wolff@t-online.de
Subject: Re: other/8948: [3.3 regression] Definition of __i686 causes big Problems
Date: Wed, 8 Jan 2003 11:37:08 +0100

 On  7 Jan, Joe Buck wrote:
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8948
 > 
 > The definition of __i686 has been present in gcc all along; removing it will
 > cause other regressions (any code that depends on it will break), so 
 > that's not an
 > option.
 > 
 > Will glibc-2.3.1 build with older gcc's?  If so, why isn't there trouble 
 > from
 > sysdep.h in such cases?
 > 
 > Volker, you are calling this a regression, but do older gcc's actually work?
 > If so, how?  They define __i686 too, in exactly the same way.
 
 I marked it as a regression according to the submitter's remark "so this
 library cannot be compiled any more for i686". I didn't actually check,
 but the problem sounded severe, so that I marked it as a regresion
 anyway, just to be sure that it gets attention.
 
 I should have been more explicit about that, sorry.
 
 Regards,
 Volker
 
 

Re: other/8948: [3.3 regression] Definition of __i686 causes big Problems

[Joe Buck]

The following reply was made to PR other/8948; it has been noted by GNATS.

From: Joe Buck <jbuck@synopsys.com>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, norbert_wolff@t-online.de,
   reichelt@igpm.rwth-aachen.de
Cc:  
Subject: Re: other/8948: [3.3 regression] Definition of __i686 causes big
 Problems
Date: Tue, 07 Jan 2003 17:51:19 -0800

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8948
 
 The definition of __i686 has been present in gcc all along; removing it will
 cause other regressions (any code that depends on it will break), so 
 that's not an
 option.
 
 Will glibc-2.3.1 build with older gcc's?  If so, why isn't there trouble 
 from
 sysdep.h in such cases?
 
 Volker, you are calling this a regression, but do older gcc's actually work?
 If so, how?  They define __i686 too, in exactly the same way.
 
 

Re: other/8948: [3.3 regression] Definition of __i686 causes big Problems

[reichelt]

Old Synopsis: Definition of __i686 causes big Problems
New Synopsis: [3.3 regression] Definition of __i686 causes big Problems

State-Changed-From-To: open->analyzed
State-Changed-By: reichelt
State-Changed-When: Mon Dec 16 09:23:47 2002
State-Changed-Why:
    Not being able to compile glibc-2.3.1 sounds like a regression.
    However, I'm not sure whether this is really a gcc bug.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8948