public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Tue, 16 Feb 2021 15:30:44 +0000	[thread overview]
Message-ID: <bug-98096-4-Q2evl8SPUn@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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>:

https://gcc.gnu.org/g:72d78655a91bb2f89ac4432cfd6374380d6f9987

commit r11-7256-g72d78655a91bb2f89ac4432cfd6374380d6f9987
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Tue Feb 16 10:27:56 2021 -0500

    [PR98096] inline-asm: Take inout operands into account for access to labels
by names.

    GCC splits inout operands into output and new matched input operands
    during gimplfication.  Addressing operands by name or number is not
    problem as the new input operands are added at the end of existing
    input operands.  However it became a problem for labels in asm goto
    with output reloads.  Addressing labels should take into account the
    new input operands.  The patch solves the problem.

    gcc/ChangeLog:

            PR inline-asm/98096
            * stmt.c (resolve_operand_name_1): Take inout operands into account
            for access to labels by names.
            * doc/extend.texi: Describe counting operands for accessing labels.

    gcc/testsuite/ChangeLog:

            PR inline-asm/98096
            * gcc.c-torture/compile/pr98096.c: New.

  parent reply	other threads:[~2021-02-16 15:30 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 [this message]
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

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-Q2evl8SPUn@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).