public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98737] Atomic operation on x86 no optimized to use flags
Date: Tue, 19 Jan 2021 07:55:59 +0000 [thread overview]
Message-ID: <bug-98737-4-VIugoNIsUh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98737-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98737
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2021-01-19
Keywords| |missed-optimization
Ever confirmed|0 |1
Target|x86 |x86_64-*-* i?86-*-*
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. Probably difficult to achieve since the atomics map to
parallel/UNSPEC:
(insn 7 6 8 (parallel [
(set (reg:DI 83 [ _2 ])
(unspec_volatile:DI [
(mem/v:DI (symbol_ref:DI ("a") [flags 0x2] <var_decl
0x7ffff7ff5b40 a>) [-1 S8 A64])
(const_int 3 [0x3])
] UNSPECV_XCHG))
(set (mem/v:DI (symbol_ref:DI ("a") [flags 0x2] <var_decl
0x7ffff7ff5b40 a>) [-1 S8 A64])
(plus:DI (mem/v:DI (symbol_ref:DI ("a") [flags 0x2] <var_decl
0x7ffff7ff5b40 a>) [-1 S8 A64])
(reg:DI 86)))
(clobber (reg:CC 17 flags))
]) "t.c":5:10 -1
(nil))
next prev parent reply other threads:[~2021-01-19 7:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 19:59 [Bug target/98737] New: " drepper.fsp+rhbz at gmail dot com
2021-01-19 7:55 ` rguenth at gcc dot gnu.org [this message]
2021-01-19 8:37 ` [Bug target/98737] " ubizjak at gmail dot com
2021-01-19 9:53 ` redi at gcc dot gnu.org
2021-01-19 10:01 ` jakub at gcc dot gnu.org
2021-01-26 15:09 ` jakub at gcc dot gnu.org
2021-01-26 16:45 ` drepper.fsp+rhbz at gmail dot com
2021-01-26 17:11 ` jakub at gcc dot gnu.org
2021-01-26 20:10 ` drepper.fsp+rhbz at gmail dot com
2021-12-14 10:20 ` jakub at gcc dot gnu.org
2022-01-03 13:17 ` cvs-commit at gcc dot gnu.org
2022-01-12 15:50 ` jakub at gcc dot gnu.org
2022-01-14 11:07 ` cvs-commit 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-98737-4-VIugoNIsUh@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).