From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH 2/7] PowerPC tests: Add PLI/PADDI tests.
Date: Sat, 27 Jun 2020 13:55:16 -0500 [thread overview]
Message-ID: <20200627185516.GO3598@gate.crashing.org> (raw)
In-Reply-To: <20200627054923.GA27951@ibm-tinman.the-meissners.org>
On Sat, Jun 27, 2020 at 01:49:23AM -0400, Michael Meissner wrote:
> On Thu, Jun 25, 2020 at 11:52:50AM -0500, Segher Boessenkool wrote:
> > On Mon, Jun 01, 2020 at 03:53:37PM -0400, Michael Meissner wrote:
> > > Add tests for -mcpu=future that test the generation of PADDI (and PLI which
> > > becomes PADDI).
> > >
> > > 2020-06-01 Michael Meissner <meissner@linux.ibm.com>
> > >
> > > * gcc.target/powerpc/prefix-add.c: New test.
> > > * gcc.target/powerpc/prefix-si-constant.c: New test.
> > > * gcc.target/powerpc/prefix-di-constant.c: New test.
> >
> > This is okay for trunk (with required changes: -mdejagnu-cpu=power10,
> > and the selector names have changed to be something with power10 instead
> > of something with future; please retest before commit).
>
> Done. I was just about to resubmit the patches with the -mcpu=power10 changes.
> I did retest on power8/power9 little endian, and power8 big endian (both
> 32/64-bit). In running the tests, I discovered 3 of the tests that needed
> ILP64 to test the particular code that I was looking for that I previously
> hadn't flagged.
Please post what you committed, then?
Segher
next prev parent reply other threads:[~2020-06-27 18:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 19:53 PowerPC tests for -mcpu=future Michael Meissner
2020-06-01 19:53 ` [PATCH 1/7] PowerPC tests: Add prefixed/pcrel tests Michael Meissner
2020-06-09 1:09 ` Segher Boessenkool
2020-06-01 19:53 ` [PATCH 2/7] PowerPC tests: Add PLI/PADDI tests Michael Meissner
2020-06-25 16:52 ` Segher Boessenkool
2020-06-27 5:49 ` Michael Meissner
2020-06-27 18:55 ` Segher Boessenkool [this message]
2020-06-29 18:23 ` Michael Meissner
2020-06-29 18:42 ` Segher Boessenkool
2020-06-30 5:58 ` Michael Meissner
2020-07-01 0:51 ` Segher Boessenkool
2020-06-27 5:57 ` Michael Meissner
2020-06-27 18:58 ` Segher Boessenkool
2020-06-01 19:53 ` [PATCH 3/7] PowerPC tests: Add prefixed vs. DS/DQ instruction tests Michael Meissner
2020-06-25 16:54 ` Segher Boessenkool
2020-06-01 19:53 ` [PATCH 4/7] PowerPC test: Add prefixed no update test Michael Meissner
2020-06-25 16:58 ` Segher Boessenkool
2020-06-01 19:53 ` [PATCH 5/7] PowerPC tests: Prefixed insn with large offsets Michael Meissner
2020-06-01 19:53 ` [PATCH 6/7] PowerPC tests: Add PC-relative tests Michael Meissner
2020-06-01 22:45 ` will schmidt
2020-06-03 3:43 ` Michael Meissner
2020-06-01 19:53 ` [PATCH 7/7] PowerPC test: Add prefixed stack protect test Michael Meissner
2020-06-25 17:18 ` Segher Boessenkool
2020-06-27 5:50 ` Michael Meissner
2020-06-27 18:44 ` Segher Boessenkool
2020-06-01 22:45 ` PowerPC tests for -mcpu=future will schmidt
2020-06-04 17:03 ` [PATCH 5/7, V2] PowerPC tests: Prefixed insn with large offsets Michael Meissner
2020-06-25 17:09 ` Segher Boessenkool
2020-06-27 5:55 ` Michael Meissner
2020-06-27 18:53 ` Segher Boessenkool
2020-06-04 17:05 ` [PATCH 6/7, V2] PowerPC tests: Add PC-relative tests Michael Meissner
2020-06-25 17:15 ` Segher Boessenkool
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=20200627185516.GO3598@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.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).