public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/49123] [4.6 Regression] FAIL: gcc.c-torture/execute/pr48973-[12].c Date: Mon, 23 May 2011 13:44:00 -0000 [thread overview] Message-ID: <bug-49123-4-d3mDhVEwqQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49123-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49123 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011.05.23 13:17:55 Target Milestone|--- |4.6.1 Ever Confirmed|0 |1 --- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-23 13:17:55 UTC --- Confirmed. FRE does <bb 2>: s.f = 1; - D.2698_4 = s.f; - D.2699_5 = (unsigned int) D.2698_4; - if (D.2699_5 != 4294967295) - goto <bb 3>; - else - goto <bb 4>; - -<bb 3>: + D.2698_4 = 1; + D.2699_5 = 1; so it fails to properly sign-extend D.2698_4.
next prev parent reply other threads:[~2011-05-23 13:34 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-23 13:29 [Bug lto/49123] New: " hjl.tools at gmail dot com 2011-05-23 13:34 ` [Bug lto/49123] " rguenth at gcc dot gnu.org 2011-05-23 13:44 ` rguenth at gcc dot gnu.org [this message] 2011-05-23 13:45 ` rguenth at gcc dot gnu.org 2011-05-23 13:46 ` jakub at gcc dot gnu.org 2011-05-23 13:52 ` rguenth at gcc dot gnu.org 2011-05-23 14:17 ` jakub at gcc dot gnu.org 2011-05-23 14:23 ` rguenth at gcc dot gnu.org 2011-05-23 15:20 ` hjl.tools at gmail dot com 2011-05-23 20:55 ` jakub at gcc dot gnu.org 2011-05-23 20:56 ` jakub at gcc dot gnu.org 2011-05-23 21:02 ` 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-49123-4-d3mDhVEwqQ@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).