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 tree-optimization/60766] [4.8/4.9 Regression] Wrong optimization with -O2 Date: Sat, 05 Apr 2014 00:05:00 -0000 [thread overview] Message-ID: <bug-60766-4-JKQaLzJRXn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60766-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60766 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Target| |x86_64-*-*-* Known to work| |4.4.5 Target Milestone|--- |4.8.3 Summary|Wrong optimization with -O2 |[4.8/4.9 Regression] Wrong | |optimization with -O2 Known to fail| |4.9.0 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Looks like IV-opt is creating some overflows that were not there in the original code. Fails with: g++ (GCC) 4.9.0 20131026 (experimental) [trunk revision 204095] I have not updated my compiler since then.
next parent reply other threads:[~2014-04-05 0:05 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-60766-4@http.gcc.gnu.org/bugzilla/> 2014-04-05 0:05 ` pinskia at gcc dot gnu.org [this message] 2014-04-05 8:04 ` Joost.VandeVondele at mat dot ethz.ch 2014-04-06 8:20 ` netheril96 at gmail dot com 2014-04-06 12:44 ` mikpelinux at gmail dot com 2014-04-07 10:26 ` [Bug tree-optimization/60766] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org 2014-04-07 14:04 ` rguenth at gcc dot gnu.org 2014-04-07 14:10 ` [Bug tree-optimization/60766] [4.7/4.8 " rguenth at gcc dot gnu.org 2014-05-06 9:02 ` rguenth at gcc dot gnu.org 2014-05-06 9:03 ` [Bug tree-optimization/60766] [4.7 " rguenth at gcc dot gnu.org 2014-06-12 13:38 ` rguenth 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-60766-4-JKQaLzJRXn@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).