public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/67830] New: wrong code at -O1 and above on x86_64-linux-gnu Date: Sat, 03 Oct 2015 05:38:00 -0000 [thread overview] Message-ID: <bug-67830-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67830 Bug ID: 67830 Summary: wrong code at -O1 and above on x86_64-linux-gnu Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: su at cs dot ucdavis.edu Target Milestone: --- The current gcc trunk mis-compiles the following code on x86_64-linux-gnu at -O1 and above in both 32-bit and 64-bit modes. This is a regression from 5.2.x. $ gcc-trunk -v Using built-in specs. COLLECT_GCC=gcc-trunk COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/6.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-trunk/configure --prefix=/usr/local/gcc-trunk --enable-languages=c,c++ --disable-werror --enable-multilib Thread model: posix gcc version 6.0.0 20151002 (experimental) [trunk revision 228389] (GCC) $ $ gcc-trunk -O0 small.c; ./a.out $ gcc-5.2 -O1 small.c; ./a.out $ $ gcc-trunk -O1 small.c $ ./a.out Aborted (core dumped) $ ---------------------------- int a, b, *g, h; unsigned char c, d; int main () { int f, e = -2; b = e; g = &b; h = c = a + 1; f = d - h; *g &= f; if (b != -2) __builtin_abort (); return 0; }
next reply other threads:[~2015-10-03 5:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-03 5:38 su at cs dot ucdavis.edu [this message] 2015-10-05 8:32 ` [Bug tree-optimization/67830] [6 Regression] " rguenth at gcc dot gnu.org 2015-10-05 8:43 ` rguenth at gcc dot gnu.org 2015-10-05 10:11 ` mpolacek at gcc dot gnu.org 2015-10-05 18:54 ` law at redhat dot com 2015-10-23 19:17 ` law at redhat dot com 2015-10-23 19:17 ` law 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-67830-4@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).