From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Paul A. Clarke" <pc@us.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/3] rs6000: Move g++.dg/ext powerpc tests to g++.target
Date: Tue, 22 Feb 2022 12:24:28 -0600 [thread overview]
Message-ID: <20220222182428.GZ614@gate.crashing.org> (raw)
In-Reply-To: <20220221211747.53681-2-pc@us.ibm.com>
Hi!
On Mon, Feb 21, 2022 at 03:17:45PM -0600, Paul A. Clarke wrote:
> Also adjust DejaGnu directives, as specifically requiring "powerpc*-*-*" is no
> longer required.
>
> 2021-02-21 Paul A. Clarke <pc@us.ibm.com>
>
> gcc/testsuite
> * g++.dg/ext/altivec-1.C: Move to g++.target/powerpc, adjust dg
> directives.
> * g++.dg/ext/altivec-2.C: Likewise.
> * g++.dg/ext/altivec-3.C: Likewise.
> * g++.dg/ext/altivec-4.C: Likewise.
> * g++.dg/ext/altivec-5.C: Likewise.
> * g++.dg/ext/altivec-6.C: Likewise.
> * g++.dg/ext/altivec-7.C: Likewise.
> * g++.dg/ext/altivec-8.C: Likewise.
> * g++.dg/ext/altivec-9.C: Likewise.
> * g++.dg/ext/altivec-10.C: Likewise.
> * g++.dg/ext/altivec-11.C: Likewise.
> * g++.dg/ext/altivec-12.C: Likewise.
> * g++.dg/ext/altivec-13.C: Likewise.
> * g++.dg/ext/altivec-14.C: Likewise.
> * g++.dg/ext/altivec-15.C: Likewise.
> * g++.dg/ext/altivec-16.C: Likewise.
> * g++.dg/ext/altivec-17.C: Likewise.
> * g++.dg/ext/altivec-18.C: Likewise.
> * g++.dg/ext/altivec-cell-1.C: Likewise.
> * g++.dg/ext/altivec-cell-2.C: Likewise.
> * g++.dg/ext/altivec-cell-3.C: Likewise.
> * g++.dg/ext/altivec-cell-4.C: Likewise.
> * g++.dg/ext/altivec-cell-5.C: Likewise.
> * g++.dg/ext/altivec-types-1.C: Likewise.
> * g++.dg/ext/altivec-types-2.C: Likewise.
> * g++.dg/ext/altivec-types-3.C: Likewise.
> * g++.dg/ext/altivec-types-4.C: Likewise.
> * g++.dg/ext/undef-bool-1.C: Likewise.
Okay for trunk. Thanks!
Segher
next prev parent reply other threads:[~2022-02-22 18:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 21:17 [PATCH 0/3] rs6000: Move g++.dg " Paul A. Clarke
2022-02-21 21:17 ` [PATCH 1/3] rs6000: Move g++.dg/ext " Paul A. Clarke
2022-02-22 18:24 ` Segher Boessenkool [this message]
2022-02-21 21:17 ` [PATCH 2/3] rs6000: Move g++.dg powerpc PR " Paul A. Clarke
2022-02-23 0:41 ` Segher Boessenkool
2022-02-23 1:56 ` Paul A. Clarke
2022-03-08 20:03 ` [PING PATCH " Paul A. Clarke
2022-03-29 15:32 ` [PING^2 " Paul A. Clarke
2022-03-29 19:53 ` [PATCH " Segher Boessenkool
2022-02-21 21:17 ` [PATCH 3/3] rs6000: Move more g++.dg powerpc " Paul A. Clarke
2022-03-08 19:59 ` [PING PATCH " Paul A. Clarke
2022-03-29 15:35 ` [PING^2 " Paul A. Clarke
2022-03-29 20:16 ` [PATCH " Segher Boessenkool
2022-02-22 18:28 ` [PATCH 0/3] rs6000: Move " Segher Boessenkool
2022-02-22 19:21 ` Paul A. Clarke
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=20220222182428.GZ614@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=pc@us.ibm.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).