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/96189] Failure to use eflags from cmpxchg on x86 Date: Wed, 15 Jul 2020 06:41:53 +0000 [thread overview] Message-ID: <bug-96189-4-0pa4TbvKZW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96189-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96189 Uroš Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2020-07-15 Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail dot com --- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> --- Created attachment 48877 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48877&action=edit Prototype patch Introduce peephole2 pattern that removes the comparison in certain cases. Doubleword cmpxchg is not handled, the doubleword comparison sequence is just too complicated in this late stage of compilation.
next prev parent reply other threads:[~2020-07-15 6:41 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-13 19:44 [Bug target/96189] New: " gabravier at gmail dot com 2020-07-13 19:55 ` [Bug target/96189] " gabravier at gmail dot com 2020-07-15 6:41 ` ubizjak at gmail dot com [this message] 2020-07-15 20:01 ` ubizjak at gmail dot com 2020-07-15 20:02 ` ubizjak at gmail dot com 2020-07-16 7:05 ` ubizjak at gmail dot com 2020-07-16 7:23 ` rguenther at suse dot de 2020-07-16 18:13 ` cvs-commit at gcc dot gnu.org 2020-11-20 15:12 ` 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-96189-4-0pa4TbvKZW@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).