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 rtl-optimization/54524] [4.6/4.7/4.8 Regression] Spurious add on sum of bitshifts (forward-propagate issue) Date: Wed, 19 Sep 2012 08:46:00 -0000 [thread overview] Message-ID: <bug-54524-4-TcyCCZESfJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54524-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54524 --- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-09-19 08:46:37 UTC --- Still non-canonical RTL should not result in wrong-code.
next prev parent reply other threads:[~2012-09-19 8:46 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-08 9:28 [Bug rtl-optimization/54524] New: Spurious add on sum of bitshifts jan.smets@alcatel-lucent.com 2012-09-08 13:19 ` [Bug rtl-optimization/54524] " jan.smets@alcatel-lucent.com 2012-09-18 8:22 ` [Bug rtl-optimization/54524] Spurious add on sum of bitshifts (forward-propagate issue) jan.smets@alcatel-lucent.com 2012-09-18 12:42 ` jan.smets@alcatel-lucent.com 2012-09-18 13:06 ` [Bug rtl-optimization/54524] [4.6/4.7/4.8 Regression] " rguenth at gcc dot gnu.org 2012-09-18 21:49 ` jan.smets@alcatel-lucent.com 2012-09-19 1:39 ` pinskia at gcc dot gnu.org 2012-09-19 8:46 ` rguenth at gcc dot gnu.org [this message] 2012-09-22 22:26 ` pinskia at gcc dot gnu.org 2012-11-02 23:33 ` pinskia at gcc dot gnu.org 2012-11-02 23:34 ` [Bug rtl-optimization/54524] [4.6/4.7 " pinskia at gcc dot gnu.org 2012-11-03 18:25 ` jan.smets@alcatel-lucent.com 2012-12-03 15:43 ` rguenth at gcc dot gnu.org 2013-01-07 13:31 ` jan.smets@alcatel-lucent.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-54524-4-TcyCCZESfJ@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).