public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/67344] PowerPC unrecognizable insn Date: Tue, 25 Aug 2015 19:33:00 -0000 [thread overview] Message-ID: <bug-67344-4-RcGugvBt5C@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67344-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67344 --- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> --- Author: segher Date: Tue Aug 25 19:32:28 2015 New Revision: 227182 URL: https://gcc.gnu.org/viewcvs?rev=227182&root=gcc&view=rev Log: rs6000: Fix PR67344 The "*and<mode>3_imm_dot_shifted" pattern is a define_insn_and_split, like most "dot" patterns: if its output is not assigned cr0 but some other cr reg, it splits to a non-dot insn and a compare. Unfortunately that non-dot insn will clobber cr0 as well. We could add another clobber (with "=X,x"), but then that second alternative is never useful; instead, just remove that second alternative. 2015-08-25 Segher Boessenkool <segher@kernel.crashing.org> PR target/67344 * config/rs6000/rs6000.md (*and<mode>3_imm_dot_shifted): Change to a define_insn, remove second alternative. Modified: trunk/gcc/ChangeLog trunk/gcc/config/rs6000/rs6000.md
next prev parent reply other threads:[~2015-08-25 19:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-24 22:57 [Bug rtl-optimization/67344] New: " anton at samba dot org 2015-08-25 0:17 ` [Bug target/67344] " amodra at gmail dot com 2015-08-25 0:52 ` segher at gcc dot gnu.org 2015-08-25 3:37 ` anton at samba dot org 2015-08-25 19:33 ` segher at gcc dot gnu.org [this message] 2015-08-25 19:38 ` segher 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-67344-4-RcGugvBt5C@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).