public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110039] [14 Regression] FAIL: gcc.target/aarch64/rev16_2.c scan-assembler-times rev16\\tw[0-9]+ 2 Date: Wed, 31 May 2023 06:53:25 +0000 [thread overview] Message-ID: <bug-110039-4-SU7PJT9gCB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110039-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110039 rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rsandifo at gcc dot gnu.org --- Comment #1 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- I guess adding an extra pattern means that we'll have three forms for this (on top of the existing alt1 and alt2 patterns). But that probably can't be helped given that the DI form has presumably not changed.
next prev parent reply other threads:[~2023-05-31 6:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-30 12:49 [Bug target/110039] New: " ktkachov at gcc dot gnu.org 2023-05-30 12:49 ` [Bug target/110039] [14 Regression] " ktkachov at gcc dot gnu.org 2023-05-31 6:53 ` rsandifo at gcc dot gnu.org [this message] 2023-05-31 13:27 ` cvs-commit at gcc dot gnu.org 2023-05-31 13:27 ` clyon 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-110039-4-SU7PJT9gCB@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).