This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: other/8948: [3.3 regression] Definition of __i686 causes bigProblems
- From: Joe Buck <jbuck at synopsys dot com>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 8 Jan 2003 01:56:01 -0000
- Subject: Re: other/8948: [3.3 regression] Definition of __i686 causes bigProblems
- Reply-to: Joe Buck <jbuck at synopsys dot com>
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.