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 rtl-optimization/63659] [4.8/4.9 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu Date: Fri, 28 Nov 2014 13:33:00 -0000 [thread overview] Message-ID: <bug-63659-4-4IKr70Sz0L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63659-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63659 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Fri Nov 28 13:32:57 2014 New Revision: 218150 URL: https://gcc.gnu.org/viewcvs?rev=218150&root=gcc&view=rev Log: Backported from mainline 2014-10-31 Jakub Jelinek <jakub@redhat.com> PR rtl-optimization/63659 * ree.c (update_reg_equal_equiv_notes): New function. (combine_set_extension, transform_ifelse): Use it. * gcc.c-torture/execute/pr63659.c: New test. Added: branches/gcc-4_9-branch/gcc/testsuite/gcc.c-torture/execute/pr63659.c Modified: branches/gcc-4_9-branch/gcc/ChangeLog branches/gcc-4_9-branch/gcc/ree.c branches/gcc-4_9-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2014-11-28 13:33 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-27 16:43 [Bug tree-optimization/63659] New: " su at cs dot ucdavis.edu 2014-10-27 16:44 ` [Bug tree-optimization/63659] [4.8/4.9/5 Regression] " jakub at gcc dot gnu.org 2014-10-27 17:32 ` [Bug rtl-optimization/63659] " jakub at gcc dot gnu.org 2014-10-27 18:36 ` jakub at gcc dot gnu.org 2014-10-31 19:48 ` jakub at gcc dot gnu.org 2014-11-18 10:32 ` [Bug rtl-optimization/63659] [4.8/4.9 " jakub at gcc dot gnu.org 2014-11-28 13:33 ` jakub at gcc dot gnu.org [this message] 2014-11-28 17:04 ` jakub at gcc dot gnu.org 2014-11-28 17:09 ` jakub 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-63659-4-4IKr70Sz0L@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).