From: Mike Stump <mikestump@comcast.net>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org, nickc@redhat.com,
richard.earnshaw@arm.com, ramana.gcc@gmail.com,
kyrylo.tkachov@arm.com,
"ro@cebitec.uni-bielefeld.de" <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: [arm] [testsuite] asm-flag-4.c: match quotes in expected message
Date: Fri, 17 Feb 2023 11:50:30 -0800 [thread overview]
Message-ID: <468D581D-764F-42D7-8066-C4299DF7EBE9@comcast.net> (raw)
In-Reply-To: <orr0uou8ai.fsf@lxoliva.fsfla.org>
On Feb 16, 2023, at 10:15 PM, Alexandre Oliva <oliva@adacore.com> wrote:
>
> Quotes were added around the "asm" keyword in the message expected by
> the test, so the test needs adjusting.
>
> Regstrapped on x86_64-linux-gnu.
> Tested on arm-vxworks7 (gcc-12) and arm-eabi (trunk).
> Ok to install?
Ok.
prev parent reply other threads:[~2023-02-17 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 6:15 Alexandre Oliva
2023-02-17 19:50 ` Mike Stump [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=468D581D-764F-42D7-8066-C4299DF7EBE9@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=nickc@redhat.com \
--cc=oliva@adacore.com \
--cc=ramana.gcc@gmail.com \
--cc=richard.earnshaw@arm.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).