public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <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: Thu, 13 Apr 2023 11:51:08 +0000	[thread overview]
Message-ID: <bug-109484-4-sGpaUxLjIR@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

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at gcc dot gnu.org

--- Comment #8 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #7)
> Similar bug.  The basic GCC expectations for inline-asm is that the whole
> assembly template after substitutions (which is for GCC mostly intentionally
> a black box) works as a single instruction which reads all its inputs (and
> that obviously doesn't mean just  the input themselves, but also any other
> register/memory used in the input) and then stores all its outputs.
> Early clobbers are the way to tell the compiler that it is not the case and
> some output is written before all the inputs are used.

Should we add this info into the doc?

  parent reply	other threads:[~2023-04-13 11:51 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
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 [this message]
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-sGpaUxLjIR@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).