This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/411] gcc defines __i686 macro, causing problems in sysdeps/i386/elf/setjmp.S
- From: "rmathew at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 16 Oct 2005 02:05:26 -0000
- Subject: [Bug libc/411] gcc defines __i686 macro, causing problems in sysdeps/i386/elf/setjmp.S
- References: <20040925224830.411.jsberg04+computing.glibc@ftml.net>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From rmathew at gmail dot com 2005-10-16 02:05 -------
(In reply to comment #4)
> We don't pass -march=i686 or equivalent to gcc when used on assembler files.
> Unless you do something wrong (like adding the -march parameter to CC or so)
> there is no problem.
Well, the "-march" bit gets added automatically if the compiler was
built with "--with-arch=pentium3". If I'm building a GCC for use on
only my machine, I would build it like this. The real questions are:
1. Does glibc *really* have to use stuff named "__i686", etc.?
2. What good does GCC achieve by predefining "__i686" when "-march=i686"?
I know you guys are not particularly interested in build failure
reports for glibc, but this particular one seems like something
that can easily be resolved between glibc and GCC.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=411
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.