public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libitm/52042] libitm.c/clone-1.c and libitm.c/stackundo.c execution tests are not pie compatible Date: Tue, 31 Jan 2012 09:48:00 -0000 [thread overview] Message-ID: <bug-52042-4-PtDldzIyXj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52042-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52042 Iain Sandoe <iains at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2012-01-31 Ever Confirmed|0 |1 --- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> 2012-01-31 08:34:33 UTC --- on i686-darwin9: make check-target-libitm RUNTESTFLAGS="--target_board=unix/-fpie\{-m32,-m64\}" clone-1 fails (m32, m64), but stackundo passes on both. I don't know whether clone is incompatible with the concept of a slidable image - or whether we just have a bug to chase down. Richard?
next prev parent reply other threads:[~2012-01-31 8:35 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-29 17:28 [Bug libitm/52042] New: " howarth at nitro dot med.uc.edu 2012-01-30 18:52 ` [Bug libitm/52042] " howarth at nitro dot med.uc.edu 2012-01-30 19:38 ` mrs at gcc dot gnu.org 2012-01-31 9:48 ` iains at gcc dot gnu.org [this message] 2012-01-31 14:16 ` [Bug libitm/52042] libitm.c/clone-1.c (all darwin) and libitm.c/stackundo.c (darwin 11) execution tests fail with -fpie iains at gcc dot gnu.org 2012-01-31 18:42 ` howarth at nitro dot med.uc.edu 2012-02-07 4:02 ` patrick.marlier at gmail dot com 2012-02-07 18:17 ` mrs at gcc dot gnu.org 2012-02-07 21:15 ` howarth at nitro dot med.uc.edu 2012-02-08 3:39 ` patrick.marlier at gmail dot com 2012-02-15 19:24 ` pmarlier at gcc dot gnu.org 2012-02-28 20:38 ` mrs at gcc dot gnu.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=bug-52042-4-PtDldzIyXj@http.gcc.gnu.org/bugzilla/ \ --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: 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).