public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "570070308 at qq dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109484] [Wrong Code][inline-asm] output operands overlap with output
Date: Wed, 12 Apr 2023 11:13:31 +0000	[thread overview]
Message-ID: <bug-109484-4-auUe18pxFv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109484-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from 。 <570070308 at qq dot com> ---
(In reply to Richard Biener from comment #3)
> (In reply to 。 from comment #2)
> > (In reply to Richard Biener from comment #1)
> > > but you clobber 'temp' early and fail to indicate that so GCC allocates the
> > > same register as part of the "+m" output.
> > 
> > The requirements you describe are not reflected in the documentation. The
> > document only says that `GCC assumpts that the assembler code consumes its
> > inputs before producing outputs`, and this code fits the assumption. First,
> > it reads the input from %1, then write the output to %0, then write the
> > output to %1. No outputs happend before inputs.
> 
> You first write to 'temp' and then read from it.  The wording applies to the
> assigned register / address, _not_ to the C variables mapped.
> 
> Note I'm not an expert here and I wonder if an output operand is the
> appropriate
> way to create a scratch register for arbitrary use.

The second instruction is $0, not %0.

  parent reply	other threads:[~2023-04-12 11:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  9:49 [Bug middle-end/109484] New: " 570070308 at qq dot com
2023-04-12 10:51 ` [Bug middle-end/109484] " rguenth at gcc dot gnu.org
2023-04-12 11:03 ` 570070308 at qq dot com
2023-04-12 11:07 ` rguenth at gcc dot gnu.org
2023-04-12 11:09 ` rguenth at gcc dot gnu.org
2023-04-12 11:13 ` 570070308 at qq dot com [this message]
2023-04-12 12:48 ` 570070308 at qq dot com
2023-04-12 13:03 ` jakub at gcc dot gnu.org
2023-04-13 11:51 ` xry111 at gcc dot gnu.org
2023-04-13 11:55 ` jakub 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-109484-4-auUe18pxFv@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).