public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/50074] [4.7 Regression] gcc.dg/sibcall-6.c execution test on x86_64 with -fPIC
Date: Sat, 19 Nov 2011 12:04:00 -0000 [thread overview]
Message-ID: <bug-50074-4-lrvBh19pTz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50074-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50074
Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amylaar at gcc dot gnu.org
--- Comment #10 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2011-11-19 11:44:00 UTC ---
(In reply to comment #9)
> I see the same on s390x. gcc.dg/sibcall-6.c starts failing with r176042.
I also see this on Epiphany.
next prev parent reply other threads:[~2011-11-19 11:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 12:44 [Bug tree-optimization/50074] New: [4.7 Regression] gcc.dg/sibcall-6.c execution test on x86_64-apple-darwin10 dominiq at lps dot ens.fr
2011-08-14 9:43 ` [Bug tree-optimization/50074] " rguenth at gcc dot gnu.org
2011-08-14 16:43 ` dominiq at lps dot ens.fr
2011-08-14 16:43 ` dominiq at lps dot ens.fr
2011-08-14 17:13 ` dominiq at lps dot ens.fr
2011-08-14 17:22 ` [Bug testsuite/50074] " hjl.tools at gmail dot com
2011-08-14 19:02 ` dominiq at lps dot ens.fr
2011-08-15 13:58 ` hjl.tools at gmail dot com
2011-08-15 14:00 ` [Bug middle-end/50074] " hjl.tools at gmail dot com
2011-08-16 9:11 ` kirill.yukhin at intel dot com
2011-10-11 13:16 ` [Bug middle-end/50074] [4.7 Regression] gcc.dg/sibcall-6.c execution test on x86_64 with -fPIC krebbel at gcc dot gnu.org
2011-10-27 10:10 ` rguenth at gcc dot gnu.org
2011-11-19 12:04 ` amylaar at gcc dot gnu.org [this message]
2011-11-19 12:26 ` amylaar at gcc dot gnu.org
2011-11-20 13:04 ` dominiq at lps dot ens.fr
2011-11-21 14:07 ` krebbel at gcc dot gnu.org
2011-11-25 13:44 ` jakub at gcc dot gnu.org
2011-11-26 11:34 ` amylaar at gcc dot gnu.org
2011-11-28 15:25 ` jakub at gcc dot gnu.org
2011-11-29 9:44 ` jakub at gcc dot gnu.org
2011-11-29 10:12 ` jakub at gcc dot gnu.org
2011-12-05 8:16 ` jakub at gcc dot gnu.org
2011-12-05 8:39 ` jakub at gcc dot gnu.org
2011-12-08 13:38 ` jakub 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-50074-4-lrvBh19pTz@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: 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).