public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110217] [avr] SREG: use BSET and BCLR instead of load/modify/write
Date: Wed, 12 Jul 2023 09:23:11 +0000	[thread overview]
Message-ID: <bug-110217-4-Ue97rzkWfx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110217-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
At least CLI / SBI won't glitch at O0, same for ATOMIC_BLOCK.

For SBI et al. you are right, they rely on insn combine. The right approach
would have been compiler built-ins or API using inline asm. But the time to
introduce such interfaces was 20 or so years ago...

  parent reply	other threads:[~2023-07-12  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  9:23 [Bug target/110217] New: " mx682x at gmail dot com
2023-06-30 16:53 ` [Bug target/110217] " gjl at gcc dot gnu.org
2023-07-10  7:18 ` mx682x at gmail dot com
2023-07-12  9:23 ` gjl at gcc dot gnu.org [this message]
2023-07-12 20:01 ` gjl 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-110217-4-Ue97rzkWfx@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).