From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [PATCH, alpha]: Fix PR 82772, could not split atomic_andsi insn
Date: Tue, 31 Oct 2017 11:02:00 -0000 [thread overview]
Message-ID: <CAFULd4bVU6Ln67jrwJpyOPm9zC=65TQ1=V6q-0dhpoauqq9LJw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
The constraint for atomic_andsi didn't fit predicate.
2017-10-31 Uros Bizjak <ubizjak@gmail.com>
PR target/82772
* config/alpha/sync.md (fetchop_constr) <and>: Change to "rINM".
Bootstrapped on alphaev68-linux-gnu, committed to mainline SVN and
release branches under obvious rule.
Uros.
[-- Attachment #2: a.diff.txt --]
[-- Type: text/plain, Size: 525 bytes --]
Index: config/alpha/sync.md
===================================================================
--- config/alpha/sync.md (revision 254243)
+++ config/alpha/sync.md (working copy)
@@ -24,7 +24,7 @@
[(plus "add_operand") (minus "reg_or_8bit_operand")
(ior "or_operand") (xor "or_operand") (and "and_operand")])
(define_code_attr fetchop_constr
- [(plus "rKL") (minus "rI") (ior "rIN") (xor "rIN") (and "riNM")])
+ [(plus "rKL") (minus "rI") (ior "rIN") (xor "rIN") (and "rINM")])
(define_expand "memory_barrier"
reply other threads:[~2017-10-31 10:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAFULd4bVU6Ln67jrwJpyOPm9zC=65TQ1=V6q-0dhpoauqq9LJw@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@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: link
Be 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).