public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsberg04+computing dot glibc at ftml dot net" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/411] gcc defines __i686 macro, causing problems in sysdeps/i386/elf/setjmp.S Date: Fri, 15 Apr 2005 20:29:00 -0000 [thread overview] Message-ID: <20050415202917.9811.qmail@sourceware.org> (raw) In-Reply-To: <20040925224830.411.jsberg04+computing.glibc@ftml.net> ------- Additional Comments From jsberg04+computing dot glibc at ftml dot net 2005-04-15 20:29 ------- Created an attachment (id=458) --> (http://sources.redhat.com/bugzilla/attachment.cgi?id=458&action=view) Patch to make it work on NPTL build I upgraded to kernel 2.6.11.7 and built a nptl glibc (2.3.5 release). Turns out the old patch didn't fix things with NPTL. Things seem to work with this patch. Note that I removed the #define from sysdep.h and instead made the #define's more narrowly targeted. Also, unstead of #undef'ing __i686, I defined it to itself as suggested by a message I found on a mailing list somewhere. I realized that I'm getting __i686 defined because I configured my gcc-3.4.3 build with --with-cpu=pentium3 --with-arch=pentium3 --with-tune=pentium3. -- What |Removed |Added ---------------------------------------------------------------------------- Attachment #219 is|0 |1 obsolete| | http://sources.redhat.com/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-04-15 20:29 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 [this message] 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 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=20050415202917.9811.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --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: linkBe 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).