public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <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 02:25:00 -0000 [thread overview]
Message-ID: <20100815022522.24415.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45286-17238@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from hjl dot tools at gmail dot com 2010-08-15 02:25 -------
(In reply to comment #0)
> http://bugs.gentoo.org/show_bug.cgi?id=283470
> kact.sa_restorer = &restore_rt; get miss compile with -fPIE
> with -fPIC the code get
> 48 8d 05 2e ff ff ff lea -0xd2(%rip),%rax # 10 <__restore_rt>
> and with -fPIE it get
> 48 8b 05 2e ff ff ff mov -0xd2(%rip),%rax # 10 <__restore_rt>
It doesn't necessarily mean wrong.
> Later on when we try to use the function in some code it segfault.
> so it would seem gcc is miscompiling the x86_64 sigaction.c code.
> specifically, this bit of sysdeps/unix/sysv/linux/x86_64/sigaction.c
Please extract a small static testcase which shows the
miscompiled sigaction.c when linking with a libc.a. I
want to know how sigaction.c is compiled.
--
hjl dot tools at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45286
next prev parent reply other threads:[~2010-08-15 2:25 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 [this message]
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
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=20100815022522.24415.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).