public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108129] nop_atomic_bit_test_and_p is too bloated
Date: Tue, 28 Mar 2023 04:34:30 +0000	[thread overview]
Message-ID: <bug-108129-4-VGV52esjwX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108129-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108129

--- Comment #4 from Hongtao.liu <crazylht at gmail dot com> ---
We may merge ATOMIC_XXX_N with SYNC_XXX_N if the "?" can be extent to optional
operand.

The only difference between them is ATOMIC_XXX_N has one more parameter, and
it's not used by the pattern match.

Currently "?" only support optional unary operation.
***
The support for ? marking extends to all unary operations including predicates
you
declare yourself with match.***

  parent reply	other threads:[~2023-03-28  4:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 15:06 [Bug tree-optimization/108129] New: " amonakov at gcc dot gnu.org
2022-12-15 15:11 ` [Bug tree-optimization/108129] " marxin at gcc dot gnu.org
2022-12-15 17:24 ` pinskia at gcc dot gnu.org
2022-12-15 17:57 ` rguenth at gcc dot gnu.org
2023-03-28  4:34 ` crazylht at gmail dot com [this message]
2023-03-28 10:51 ` rguenth at gcc dot gnu.org
2023-03-28 11:31 ` cvs-commit at gcc dot gnu.org
2023-03-28 11:35 ` rguenth 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-108129-4-VGV52esjwX@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).