public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/98096] Inconsistent operand numbering for asm goto with in-out operands
Date: Wed, 05 Jan 2022 17:54:24 +0000	[thread overview]
Message-ID: <bug-98096-4-uZSiTYqbar@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98096-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
That isn't easibly possible, the labels are really significantly different from
the implementation POV, so having them intermixed with inputs is hard.
If you don't want to count on those extra inputs, name the labels...

      parent reply	other threads:[~2022-01-05 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 13:43 [Bug inline-asm/98096] New: " jwjagersma at gmail dot com
2020-12-02 23:37 ` [Bug inline-asm/98096] " pinskia at gcc dot gnu.org
2021-02-16 15:30 ` cvs-commit at gcc dot gnu.org
2021-09-14  7:48 ` pinskia at gcc dot gnu.org
2021-12-10  1:46 ` pinskia at gcc dot gnu.org
2021-12-10 23:33 ` ndesaulniers at google dot com
2021-12-11  0:13 ` pinskia at gcc dot gnu.org
2022-01-05 17:50 ` foom at fuhm dot net
2022-01-05 17:54 ` jakub at gcc dot gnu.org [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-98096-4-uZSiTYqbar@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).