public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmathew at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/411] gcc defines __i686 macro, causing problems in sysdeps/i386/elf/setjmp.S
Date: Sun, 16 Oct 2005 02:07:00 -0000 [thread overview]
Message-ID: <20051016020526.25703.qmail@sourceware.org> (raw)
In-Reply-To: <20040925224830.411.jsberg04+computing.glibc@ftml.net>
------- 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.
next prev parent reply other threads:[~2005-10-16 2:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 22:48 [Bug libc/411] New: " jsberg04+computing dot glibc at ftml dot net
2004-10-03 2:00 ` [Bug libc/411] " jsberg04+computing dot glibc at ftml dot net
2005-04-15 20:29 ` jsberg04+computing dot glibc at ftml dot net
2005-04-15 20:35 ` jsberg04+computing dot glibc at ftml dot net
2005-08-04 5:38 ` rmathew at gmail dot com
2005-10-16 0:41 ` drepper at redhat dot com
2005-10-16 2:07 ` rmathew at gmail dot com [this message]
2006-02-07 20:15 ` jsberg04+computing dot glibc at ftml dot net
2006-02-08 9:37 ` Petr dot Salinger at seznam dot cz
2006-02-08 9:42 ` jakub at redhat dot com
2006-02-08 11:14 ` Petr dot Salinger at seznam dot cz
2006-04-21 18:25 ` drepper at redhat dot com
2010-02-24 13:38 ` davem at davemloft dot net
2010-04-15 8:20 ` jue at jue dot li
2010-08-22 10:33 ` allan at archlinux dot org
[not found] <bug-411-131@http.sourceware.org/bugzilla/>
2012-01-19 2:13 ` burtms at gmail dot com
2012-01-19 6:32 ` polacek at redhat dot com
2012-01-21 17:28 ` burtms at gmail dot com
2012-02-03 12:54 ` vapier at gentoo dot org
2012-02-08 1:48 ` jsm28 at gcc dot gnu.org
2012-02-18 0:17 ` jsm28 at gcc dot gnu.org
2012-04-22 19:36 ` carlos_odonell at mentor dot com
2014-02-16 19:22 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051016020526.25703.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).