public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/53020] __atomic_fetch_or doesn't generate `1 insn` variant
Date: Tue, 17 Apr 2012 16:55:00 -0000 [thread overview]
Message-ID: <bug-53020-4-bz0iWckim9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53020-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53020
Uros Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2012-04-17
AssignedTo|unassigned at gcc dot |ubizjak at gmail dot com
|gnu.org |
Target Milestone|--- |4.5.4
Ever Confirmed|0 |1
--- Comment #2 from Uros Bizjak <ubizjak at gmail dot com> 2012-04-17 16:54:06 UTC ---
Uh...
Index: config/i386/sync.md
===================================================================
--- config/i386/sync.md (revision 186501)
+++ config/i386/sync.md (working copy)
@@ -576,7 +576,7 @@
return "lock{%;} sub{<imodesuffix>}\t{%1, %0|%0, %1}";
})
-(define_insn "atomic_<code><mode>"
+(define_insn "atomic_<logic><mode>"
[(set (match_operand:SWI 0 "memory_operand" "+m")
(unspec_volatile:SWI
[(any_logic:SWI (match_dup 0)
next prev parent reply other threads:[~2012-04-17 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 16:21 [Bug target/53020] New: " kirill.yukhin at intel dot com
2012-04-17 16:25 ` [Bug target/53020] " kirill.yukhin at intel dot com
2012-04-17 16:55 ` ubizjak at gmail dot com [this message]
2012-04-17 17:01 ` kirill.yukhin at intel dot com
2012-04-17 17:40 ` uros at gcc dot gnu.org
2012-04-17 17:41 ` uros at gcc dot gnu.org
2012-04-17 17:57 ` ubizjak at gmail dot 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-53020-4-bz0iWckim9@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: 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).