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 middle-end/107385] [asm goto] "=r" vs "+r" for outputs along indirect edges Date: Thu, 15 Feb 2024 15:17:56 +0000 [thread overview] Message-ID: <bug-107385-4-DhlfbAS0O1@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 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:d2ebd5948bd21f54fdbc5ea99e391be59d0af64c commit r12-10159-gd2ebd5948bd21f54fdbc5ea99e391be59d0af64c Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Feb 15 15:55:25 2024 +0100 testsuite: Add testcase for already fixed PR [PR107385] This testcase has been fixed by the PR113921 fix, but unlike testcase in there this one is not target specific. 2024-02-15 Jakub Jelinek <jakub@redhat.com> PR middle-end/107385 * gcc.dg/pr107385.c: New test. (cherry picked from commit 5459a9074afabf700f055fc8164f88dadb1c39b0)
next prev parent reply other threads:[~2024-02-15 15:17 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 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 [this message] 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-DhlfbAS0O1@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: linkBe 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).