public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/45286] kact.sa_restorer = &restore_rt; in sigaction.c glibc get miss compile with -fPIE on x86_64
Date: Sun, 15 Aug 2010 21:59:00 -0000 [thread overview]
Message-ID: <20100815215941.28550.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45286-17238@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from vapier at gentoo dot org 2010-08-15 21:59 -------
we are using current GNU binutils (2.20.1). we dont use Linux binutils anymore
in Gentoo by default due to the instability and random patches that never get
mainlined into the GNU binutils. however, even with binutils-2.20.51.0.11, i
get the same behavior:
f8: 48 8b 05 11 ff ff ff mov -0xef(%rip),%rax # 10 <__restore_rt>
while the initial report is gcc-4.3.4, same behavior can be observed with
gcc-4.4.4. seems general users (like me) cannot update the Known-to-fail
field.
how can it be a linker bug if the compiled .o seems to be incorrect ? i dont
think lazy linking changes the actual code generated ?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45286
next prev parent reply other threads:[~2010-08-15 21:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 1:00 [Bug c/45286] New: " zorry at ume dot nu
2010-08-15 1:02 ` [Bug c/45286] " zorry at ume dot nu
2010-08-15 1:04 ` zorry at ume dot nu
2010-08-15 2:25 ` hjl dot tools at gmail dot com
2010-08-15 4:41 ` vapier at gentoo dot org
2010-08-15 5:40 ` hjl dot tools at gmail dot com
2010-08-15 5:49 ` vapier at gentoo dot org
2010-08-15 20:36 ` hjl dot tools at gmail dot com
2010-08-15 20:41 ` vapier at gentoo dot org
2010-08-15 20:46 ` hjl dot tools at gmail dot com
2010-08-15 21:01 ` vapier at gentoo dot org
2010-08-15 21:15 ` hjl dot tools at gmail dot com
2010-08-15 21:32 ` zorry at ume dot nu
2010-08-15 21:36 ` hjl dot tools at gmail dot com
2010-08-15 21:59 ` vapier at gentoo dot org [this message]
2010-08-15 22:12 ` rguenth at gcc dot gnu dot org
2010-08-16 11:16 ` jakub at gcc dot gnu dot org
2010-08-18 3:23 ` vapier at gentoo dot org
2010-08-18 3:29 ` hjl dot tools at gmail dot com
2010-08-18 3:39 ` vapier at gentoo dot org
2010-08-18 3:59 ` hjl dot tools at gmail dot com
[not found] <bug-45286-4@http.gcc.gnu.org/bugzilla/>
2015-07-04 15:23 ` zorry at gentoo dot org
2015-07-04 15:40 ` hjl.tools at gmail dot com
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=20100815215941.28550.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).