public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64853] [5 Regression] wrong code at -Os and above on x86_64-linux-gnu Date: Thu, 29 Jan 2015 08:11:00 -0000 [thread overview] Message-ID: <bug-64853-4-M4Sx1UxICg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64853-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64853 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-01-29 CC| |jakub at gcc dot gnu.org Target Milestone|--- |5.0 Summary|wrong code at -Os and above |[5 Regression] wrong code |on x86_64-linux-gnu |at -Os and above on | |x86_64-linux-gnu Ever confirmed|0 |1 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- This started with r217560, the first difference is during VRP2: Visiting statement: _13 = (signed char) g_68; +Match-and-simplified (signed char) g_68 to -56(OVF) Found new range for _13: [-56, -56] and various others, leading to -_10: ~[1, 254] +_10: [255, +INF] .MEM_11: VARYING -g_12: [0, 255] -_13: VARYING +g_12: [255, 255] +_13: [-56, -1] etc. Haven't checked if the changes are correct or not.
next prev parent reply other threads:[~2015-01-29 8:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-29 6:16 [Bug tree-optimization/64853] New: " su at cs dot ucdavis.edu 2015-01-29 8:11 ` jakub at gcc dot gnu.org [this message] 2015-01-29 9:18 ` [Bug tree-optimization/64853] [5 Regression] " jakub at gcc dot gnu.org 2015-01-29 9:27 ` jakub at gcc dot gnu.org 2015-01-29 9:49 ` jakub at gcc dot gnu.org 2015-01-29 9:51 ` rguenth at gcc dot gnu.org 2015-01-29 9:54 ` rguenth at gcc dot gnu.org 2015-01-29 10:37 ` rguenth at gcc dot gnu.org 2015-01-29 13:51 ` rguenth at gcc dot gnu.org 2015-01-29 13:51 ` 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-64853-4-M4Sx1UxICg@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).