public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@adacore.com>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
Cc: gcc-patches@gcc.gnu.org,
	Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
	Mike Stump <mikestump@comcast.net>,
	Nick Clifton <nickc@redhat.com>,
	Ramana Radhakrishnan <ramana.gcc@gmail.com>
Subject: Re: [PATCH v2] [testsuite] [arm] add effective target and options for pacbti tests
Date: Sat, 25 May 2024 05:20:23 -0300	[thread overview]
Message-ID: <ora5keb8vs.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <or34rh9ulo.fsf_-_@lxoliva.fsfla.org> (Alexandre Oliva's message of "Fri, 19 Apr 2024 13:37:39 -0300")

On Apr 19, 2024, Alexandre Oliva <oliva@adacore.com> wrote:

> for  gcc/testsuite/ChangeLog

> 	* gcc.target/arm/bti-1.c: Require arch, use its opts, drop skip.
> 	* gcc.target/arm/bti-2.c: Likewise.
> 	* gcc.target/arm/acle/pacbti-m-predef-11.c: Likewise.
> 	* gcc.target/arm/acle/pacbti-m-predef-12.c: Likewise.
> 	* gcc.target/arm/acle/pacbti-m-predef-7.c: Likewise.
> 	* g++.target/arm/pac-1.C: Likewise.  Drop +mve.

Ping?  https://gcc.gnu.org/pipermail/gcc-patches/2024-April/649732.html

-- 
Alexandre Oliva, happy hacker            https://FSFLA.org/blogs/lxo/
   Free Software Activist                   GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive

      reply	other threads:[~2024-05-25  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16  3:48 [PATCH] [testsuite] [arm] require arm_v8_1m_main " Alexandre Oliva
2024-04-16  8:56 ` Richard Earnshaw (lists)
2024-04-19 12:45   ` Alexandre Oliva
2024-04-19 13:13     ` Richard Earnshaw (lists)
2024-04-19 16:37       ` [PATCH v2] [testsuite] [arm] add effective target and options " Alexandre Oliva
2024-05-25  8:20         ` Alexandre Oliva [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=ora5keb8vs.fsf@lxoliva.fsfla.org \
    --to=oliva@adacore.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    --cc=nickc@redhat.com \
    --cc=ramana.gcc@gmail.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).