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/59747] [4.9 Regression] wrong code at -Os and above on x86_64-linux-gnu in 64-bit mode Date: Fri, 10 Jan 2014 13:14:00 -0000 [thread overview] Message-ID: <bug-59747-4-GlorFJTsDf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59747-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59747 --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The actual REGNO != REGNO transformation is correct, the problem is that the second extension is to a wider mode and while handling that we change the destination mode on the def_insn to an even wider mode. The code just assumes that the def insn sets the right REGNO rather than some other. So, I think it shouldn't be hard to detect that case. Then we either need to ensure the corresponding copy insn from the first extension will be adjusted to the wider mode, or for this case swap back the registers (revert to the original REGNO for the def insn and put the swap insn the other way around), or do it the other way around always (then no special casing would be needed; Jeff, what was the reason why you haven't handled (set (reg1) (expression)) (set (reg2) (any_extend (reg1)) as (set (reg1) (any_extend (expression))) (set (reg2) (reg1)) but instead (set (reg2) (any_extend (expression))) (set (reg1) (reg2)) ?).
next prev parent reply other threads:[~2014-01-10 13:14 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-10 6:19 [Bug tree-optimization/59747] New: " su at cs dot ucdavis.edu 2014-01-10 8:48 ` [Bug tree-optimization/59747] [4.9 Regression] " mpolacek at gcc dot gnu.org 2014-01-10 10:05 ` mpolacek at gcc dot gnu.org 2014-01-10 10:17 ` mpolacek at gcc dot gnu.org 2014-01-10 10:58 ` jakub at gcc dot gnu.org 2014-01-10 11:05 ` rguenth at gcc dot gnu.org 2014-01-10 11:08 ` jakub at gcc dot gnu.org 2014-01-10 13:14 ` jakub at gcc dot gnu.org [this message] 2014-01-10 16:25 ` law at redhat dot com 2014-01-10 17:14 ` law at redhat dot com 2014-01-10 17:56 ` law at redhat dot com 2014-01-15 13:11 ` trippels at gcc dot gnu.org 2014-01-15 18:14 ` law at redhat dot com 2014-01-15 18:14 ` law at gcc dot gnu.org 2014-01-16 20:11 ` dominiq at lps dot ens.fr 2014-01-16 20:12 ` dominiq at lps dot ens.fr 2014-01-16 20:12 ` dominiq at lps dot ens.fr 2014-01-16 20:20 ` jakub at gcc dot gnu.org 2014-01-16 21:05 ` dominiq at lps dot ens.fr
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-59747-4-GlorFJTsDf@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).