From: Xionghu Luo <luoxhu@linux.ibm.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Bill Schmidt <wschmidt@linux.ibm.com>,
linkw@gcc.gnu.org
Subject: Re: Ping ^ 2: [PATCH] rs6000: Remove unspecs for vec_mrghl[bhw]
Date: Wed, 13 Oct 2021 09:59:31 +0800 [thread overview]
Message-ID: <82761479-4b61-bea7-e4ec-1e7a787139b8@linux.ibm.com> (raw)
In-Reply-To: <CAGWvnyk_7-3J-PKPYRGi=3P-sC+c+hLTiFhcD2YDCXjiaOyP5A@mail.gmail.com>
Thanks David,
On 2021/10/13 06:51, David Edelsohn wrote:
> Hi, Xionghu
>
> What's the status of the \M and \m testcase beautification requested
> by Segher? Did you send an updated patch? Your messages ping the
> version prior to Segher's additional comments.
The pinged link already answered Segher's questions and included a patch
pasted in it. To follow Segher's preference ;), I just post a v2 patch
here:
https://gcc.gnu.org/pipermail/gcc-patches/2021-October/581497.html
\M and \m are actually not quite necessary to the testcase
gcc.target/powerpc/builtins-1.c since it is built with
"-mdejagnu-cpu=power8 -O0 -mno-fold-gimple -dp", so the testcase also counts
the generated instruction patterns.
>
> It seems that the changes to the patterns are complete, but there are
> remaining questions about the testcase style and if the instruction
> counts are ideal. I trust that the instruction counts match the
> behavior after the patch, but it seemed that Segher wanted to confirm
> that the counts are the values desired / expected from optimal code
> generation. The counts are the total for the file, which doesn't
> communicate if the sequences themselves are optimal.
Will rebase and retest after Segher's review of the v2 patch.
--
Thanks,
Xionghu
prev parent reply other threads:[~2021-10-13 1:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 9:02 Xionghu Luo
2021-06-07 5:09 ` Ping: " Xionghu Luo
2021-06-08 23:25 ` Segher Boessenkool
2021-06-09 8:03 ` Xionghu Luo
2021-06-09 11:57 ` Segher Boessenkool
2021-06-30 1:47 ` Ping: " Xionghu Luo
2021-09-06 0:54 ` Ping ^ 2: " Xionghu Luo
2021-10-12 22:51 ` David Edelsohn
2021-10-13 1:59 ` Xionghu Luo [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=82761479-4b61-bea7-e4ec-1e7a787139b8@linux.ibm.com \
--to=luoxhu@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@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).