From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
gcc-patches@gcc.gnu.org, Michael Matz <matz@suse.de>
Subject: Re: [PATCH][RFC] Introduce BIT_FIELD_INSERT
Date: Fri, 20 May 2016 11:52:00 -0000 [thread overview]
Message-ID: <20160520115209.GK28550@tucnak.redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1605201339460.18037@t29.fhfr.qr>
On Fri, May 20, 2016 at 01:41:01PM +0200, Richard Biener wrote:
> I'd say ppc and aarch64 are fine. Thanks for noticing.
So like this then?
2016-05-20 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/29756
gcc.dg/tree-ssa/vector-6.c: Add -Wno-psabi -w to dg-options.
Add -msse2 for x86 and -maltivec for powerpc. Use scan-tree-dump-times
only on selected targets where V4SImode vectors are known to be
supported.
--- gcc/testsuite/gcc.dg/tree-ssa/vector-6.c.jj 2016-05-20 12:44:33.000000000 +0200
+++ gcc/testsuite/gcc.dg/tree-ssa/vector-6.c 2016-05-20 13:49:19.880961132 +0200
@@ -1,5 +1,7 @@
/* { dg-do compile } */
-/* { dg-options "-O -fdump-tree-ccp1" } */
+/* { dg-options "-O -fdump-tree-ccp1 -Wno-psabi -w" } */
+/* { dg-additional-options "-msse2" { target i?86-*-* x86_64-*-* } } */
+/* { dg-additional-options "-maltivec" { target powerpc_altivec_ok } } */
typedef int v4si __attribute__((vector_size (4 * sizeof (int))));
@@ -30,4 +32,4 @@ v4si test4 (v4si v, int i)
return v;
}
-/* { dg-final { scan-tree-dump-times "Now a gimple register: v" 4 "ccp1" } } */
+/* { dg-final { scan-tree-dump-times "Now a gimple register: v" 4 "ccp1" { target { { i?86-*-* x86_64-*-* aarch64*-*-* spu*-*-* } || { powerpc_altivec_ok } } } } } */
Jakub
next prev parent reply other threads:[~2016-05-20 11:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 10:51 Richard Biener
2016-05-16 0:55 ` Bill Schmidt
2016-05-16 12:37 ` Bill Schmidt
2016-05-17 7:52 ` Richard Biener
2016-05-16 8:24 ` Eric Botcazou
2016-05-17 7:50 ` Richard Biener
2016-05-17 8:13 ` Eric Botcazou
2016-05-17 15:19 ` Michael Matz
2016-05-19 13:23 ` Richard Biener
2016-05-19 15:21 ` Eric Botcazou
2016-05-20 8:59 ` Richard Biener
2016-05-20 11:25 ` Jakub Jelinek
2016-05-20 11:41 ` Richard Biener
2016-05-20 11:52 ` Jakub Jelinek [this message]
2016-05-20 11:53 ` Richard Biener
2016-05-20 14:11 ` Andi Kleen
2016-05-20 15:12 ` Marc Glisse
2016-05-20 15:54 ` Andi Kleen
2016-05-20 16:08 ` Jakub Jelinek
2016-05-20 19:25 ` Richard Biener
2016-05-20 17:08 ` Marc Glisse
2018-11-15 1:27 ` Andrew Pinski
2018-11-15 8:29 ` Richard Biener
2018-11-15 8:31 ` Richard Biener
2019-12-17 2:41 ` Andrew Pinski
2019-12-17 3:25 ` Andrew Pinski
2020-01-07 7:37 ` Richard Biener
2020-01-07 9:40 ` Andrew Pinski
2020-01-07 10:04 ` Richard Biener
2020-01-07 11:14 ` Richard Sandiford
2020-01-07 11:38 ` Richard Biener
2020-01-07 11:52 ` Richard Sandiford
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=20160520115209.GK28550@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
--cc=rguenther@suse.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).