public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/57124] 254.gap@spec2000 got miscompare after r198413 Date: Wed, 01 May 2013 05:13:00 -0000 [thread overview] Message-ID: <bug-57124-4-J7XCT0YXC6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57124-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57124 --- Comment #2 from Jeffrey A. Law <law at redhat dot com> 2013-05-01 05:13:38 UTC --- __attribute__ ((noinline)) foo(short unsigned int *p1, short unsigned int *p2) { short unsigned int x1, x4; int x2, x3, x5, x6; unsigned int x7; x1 = *p1; x2 = (int) x1; x3 = x2 * 65536; x4 = *p2; x5 = (int) x4; x6 = x3 + x4; x7 = (unsigned int) x6; if (x7 <= 268435455U) abort (); exit (0); } main() { short unsigned int x, y; x = -5; y = -10; foo (&x, &y); } Is a much reduced testcase. Ultimately we have a range for x6 that's [0, +INF(OVF)] at which point it's not safe to replace x7 with x6 in the conditional.
next prev parent reply other threads:[~2013-05-01 5:13 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-30 12:29 [Bug tree-optimization/57124] New: " izamyatin at gmail dot com 2013-04-30 15:43 ` [Bug tree-optimization/57124] " law at redhat dot com 2013-04-30 19:20 ` law at redhat dot com 2013-05-01 5:13 ` law at redhat dot com [this message] 2013-05-02 8:01 ` rguenth at gcc dot gnu.org 2013-05-07 4:25 ` law at redhat dot com 2013-05-15 15:23 ` ysrumyan at gmail dot com 2013-05-16 9:07 ` rguenth at gcc dot gnu.org 2013-05-24 17:22 ` law at redhat 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=bug-57124-4-J7XCT0YXC6@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).