public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/53147] [4.7/4.8 Regression] gcc apparently miscompiles clang-3.1(or trunk) Date: Sat, 28 Apr 2012 07:31:00 -0000 [thread overview] Message-ID: <bug-53147-4-lCGK4G30ZU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53147-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53147 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2012-04-28 Ever Confirmed|0 |1 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-04-28 07:31:13 UTC --- Can you attach the preprocessed source for the file which is considered to be miscompiled? Then maybe we can figure out for sure if it is a GCC issue or a clang issue.
next prev parent reply other threads:[~2012-04-28 7:31 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-27 21:11 [Bug middle-end/53147] New: " markus at trippelsdorf dot de 2012-04-27 21:17 ` [Bug middle-end/53147] " markus at trippelsdorf dot de 2012-04-27 21:25 ` pinskia at gcc dot gnu.org 2012-04-27 21:28 ` markus at trippelsdorf dot de 2012-04-28 7:04 ` markus at trippelsdorf dot de 2012-04-28 7:28 ` pinskia at gcc dot gnu.org 2012-04-28 7:31 ` pinskia at gcc dot gnu.org [this message] 2012-04-28 9:32 ` markus at trippelsdorf dot de 2012-04-28 9:38 ` markus at trippelsdorf dot de 2012-04-28 10:02 ` pinskia at gcc dot gnu.org 2012-04-28 10:05 ` pinskia at gcc dot gnu.org 2012-04-28 10:41 ` markus at trippelsdorf dot de
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-53147-4-lCGK4G30ZU@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).