From: Alexandre Oliva <oliva@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: nickc@redhat.com, richard.earnshaw@arm.com, ramana.gcc@gmail.com,
kyrylo.tkachov@arm.com
Subject: Re: [PATCH] [PR51534] [arm] split out pr51534 test for softfp
Date: Fri, 03 Mar 2023 05:28:09 -0300 [thread overview]
Message-ID: <orlekejl2e.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <orbklssr0v.fsf@lxoliva.fsfla.org> (Alexandre Oliva's message of "Fri, 17 Feb 2023 04:13:52 -0300")
On Feb 17, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
> PR target/51534
> * gcc.target/arm/pr51534.c: Split softfp variant into...
> * gcc.target/arm/pr51534s.c: ... this, and support ARM too.
Ping?
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612189.html
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2023-03-03 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 7:13 Alexandre Oliva
2023-03-03 8:28 ` Alexandre Oliva [this message]
2023-03-03 9:14 ` Kyrylo Tkachov
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=orlekejl2e.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=nickc@redhat.com \
--cc=ramana.gcc@gmail.com \
--cc=richard.earnshaw@arm.com \
/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).