public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dimitri.gorokhovik at free dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109903] Register misallocation in hand-crafted asm insn, no diagnostics produced
Date: Thu, 18 May 2023 16:09:38 +0000 [thread overview]
Message-ID: <bug-109903-4-jGcOLwJgLP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109903-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109903
--- Comment #6 from Dimitri Gorokhovik <dimitri.gorokhovik at free dot fr> ---
Thank you Andrew, I indeed see now the early-clobber effect of this code.
It isn't that we don't read documentation (we do time to time), rather our real
asm statement has more output ops and more elementary instructions in the
template, so the early-clobber effect doesn't jump to the eye quite as easily.
I guess we have to mask all output ops as early clobbers.
prev parent reply other threads:[~2023-05-18 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 14:59 [Bug target/109903] New: " dimitri.gorokhovik at free dot fr
2023-05-18 15:02 ` [Bug target/109903] " pinskia at gcc dot gnu.org
2023-05-18 15:04 ` pinskia at gcc dot gnu.org
2023-05-18 15:05 ` pinskia at gcc dot gnu.org
2023-05-18 15:28 ` dimitri.gorokhovik at free dot fr
2023-05-18 15:50 ` pinskia at gcc dot gnu.org
2023-05-18 16:09 ` dimitri.gorokhovik at free dot fr [this message]
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-109903-4-jGcOLwJgLP@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).