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 middle-end/107385] [asm goto] "=r" vs "+r" for outputs along indirect edges
Date: Thu, 15 Feb 2024 08:21:20 +0000	[thread overview]
Message-ID: <bug-107385-4-AgNiznxKmX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107385-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |jakub at gcc dot gnu.org
         Resolution|---                         |DUPLICATE

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems to be fixed by the PR113921 fix.  But more test coverage doesn't hurt, so
2024-02-15  Jakub Jelinek  <jakub@redhat.com>

        PR middle-end/107385
        * gcc.target/i386/pr107385.c: New test.

--- gcc/testsuite/gcc.target/i386/pr107385.c.jj 2024-01-13 00:05:00.077372302
+0100
+++ gcc/testsuite/gcc.target/i386/pr107385.c    2024-02-15 09:18:47.711260427
+0100
@@ -0,0 +1,20 @@
+/* PR middle-end/107385 */
+/* { dg-do run } */
+/* { dg-options "-O2" } */
+
+__attribute__((noipa)) int
+foo (void)
+{
+  int x;
+  asm goto ("": "=r" (x) : "0" (15), "a" (42) :: lab);
+  x = 6;
+lab:
+  return x;
+}
+
+int
+main ()
+{
+  if (foo () != 6)
+    __builtin_abort ();
+}

*** This bug has been marked as a duplicate of bug 113921 ***

  parent reply	other threads:[~2024-02-15  8:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 18:37 [Bug c/107385] New: " ndesaulniers at google dot com
2022-10-24 18:59 ` [Bug middle-end/107385] " pinskia at gcc dot gnu.org
2024-02-15  8:21 ` jakub at gcc dot gnu.org [this message]
2024-02-15 13:07 ` jakub at gcc dot gnu.org
2024-02-15 13:07 ` jakub at gcc dot gnu.org
2024-02-15 14:56 ` cvs-commit at gcc dot gnu.org
2024-02-15 15:15 ` cvs-commit at gcc dot gnu.org
2024-02-15 15:17 ` cvs-commit at gcc dot gnu.org
2024-02-15 15:21 ` cvs-commit at gcc dot gnu.org
2024-02-15 19:06 ` cvs-commit at gcc dot gnu.org
2024-02-15 19:08 ` cvs-commit at gcc dot gnu.org
2024-02-15 19:08 ` cvs-commit at gcc dot gnu.org
2024-02-15 19:09 ` cvs-commit 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-107385-4-AgNiznxKmX@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).