From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: Richard Biener <rguenther@suse.de>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Bill Schmidt <wschmidt@linux.ibm.com>
Subject: Re: [PATCH V4] PR88497 - Extend reassoc for vector bit_field_ref
Date: Tue, 09 Jul 2019 16:51:00 -0000 [thread overview]
Message-ID: <20190709164131.GL30355@gate.crashing.org> (raw)
In-Reply-To: <ee9c5e58-341c-193c-0ec6-be6158fbf0c5@linux.ibm.com>
On Tue, Jul 09, 2019 at 10:28:06AM +0800, Kewen.Lin wrote:
> on 2019/7/9 ä¸å12:32, Segher Boessenkool wrote:
> > On Mon, Jul 08, 2019 at 04:07:00PM +0800, Kewen.Lin wrote:
> >> --- /dev/null
> >> +++ b/gcc/testsuite/gcc.dg/tree-ssa/pr88497-1.c
> >> @@ -0,0 +1,60 @@
> >> +/* { dg-do run } */
> >> +/* { dg-require-effective-target vect_double } */
> >> +/* { dg-require-effective-target powerpc_vsx_ok { target { powerpc*-*-* } } } */
> >
> > For "dg-do run" tests, you need "powerpc_vsx_hw". "_ok" only tests if
> > the assembler can handle VSX instructions, not whether the test system
> > can run them. (powerpc_vsx_ok is what you need for "dg-do assemble" or
> > "dg-do link" tests. It also tests if you can use -mvsx, but that doesn't
> > do what you might hope it does: you can use -mvsx together with a -mcpu=
> > that doesn't support VSX, for example).
>
> Thanks, I will update it. But sorry that I can't find "powerpc_vsx_hw" but
> "vsx_hw_available". I guess it's the one you are referring to?
Yeah, sorry. You can also use just "vsx_hw".
> And I happened
> to find the vect_double will force powerpc to check vsx_hw_available.
Yes :-) So this whole line is unnecessary.
Segher
next prev parent reply other threads:[~2019-07-09 16:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 3:33 [PATCH V3] " Kewen.Lin
2019-04-03 22:00 ` [PING] " Kewen.Lin
2019-05-05 6:15 ` Kewen.Lin
2019-05-21 2:03 ` Kewen.Lin
2019-06-11 2:46 ` [PING^4] " Kewen.Lin
2019-06-26 5:37 ` [PING^5] " Kewen.Lin
2019-07-02 12:43 ` Richard Biener
2019-07-03 3:20 ` Kewen.Lin
2019-07-03 12:21 ` Richard Biener
2019-07-08 8:14 ` [PATCH V4] " Kewen.Lin
2019-07-08 16:56 ` Segher Boessenkool
2019-07-09 2:37 ` Kewen.Lin
2019-07-09 16:51 ` Segher Boessenkool [this message]
2019-07-10 11:54 ` Richard Biener
2019-07-11 13:51 ` [PATCH V5] " Kewen.Lin
2019-07-12 10:07 ` Richard Biener
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=20190709164131.GL30355@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=rguenther@suse.de \
--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).