From: Richard Biener <rguenther@suse.de>
To: Bill Schmidt <wschmidt@linux.vnet.ibm.com>,gcc-patches@gcc.gnu.org
Cc: mikestump@comcast.net
Subject: Re: [4.8, testsuite] Correct backported fix to gcc.dg/vect/vect-33.c
Date: Tue, 16 Jun 2015 06:09:00 -0000 [thread overview]
Message-ID: <5D62F220-B403-4F6D-B5CD-365CC85BE843@suse.de> (raw)
In-Reply-To: <1434398313.2747.17.camel@gnopaine>
On June 15, 2015 9:58:33 PM GMT+02:00, Bill Schmidt <wschmidt@linux.vnet.ibm.com> wrote:
>I just was reading the gcc mailing list and realized that changes to
>4.8
>now require release manager approval. Adding Richard to the CC list
>for
>consideration. Thanks!
OK.
Richard.
>Bill
>
>On Mon, 2015-06-15 at 14:54 -0500, Bill Schmidt wrote:
>> Hi,
>>
>> When I backported support for unaligned vector load/store operations
>on
>> POWER8 to GCC 4.8, I fumbled the change for gcc.dg/vect/vect-33.c.
>One
>> of the original tests was:
>>
>> /* { dg-final { scan-tree-dump-times "Vectorizing an unaligned
>access" 0 "vect" } } */
>>
>> which I modified to
>>
>> /* { dg-final { scan-tree-dump-times "Vectorizing an unaligned
>access" 0 "vect" { target { ! vect_hw_misalign } } } } */
>>
>> This caused the test to be skipped for architectures other than
>PowerPC,
>> which was a mistake. The correct test should have been:
>>
>> /* { dg-final { scan-tree-dump-times "Vectorizing an unaligned
>access" 0 "vect" { target { { ! powerpc*-*-* } || { ! vect_hw_misalign
>} } } } } */
>>
>> which leaves things alone for other architectures.
>>
>> Ok for 4.8?
>>
>> Thanks,
>> Bill
>>
>>
>> 2015-06-15 Bill Schmidt <wschmidt@linux.vnet.ibm.com>
>>
>> * gcc.dg/vect/vect-33.c: Don't exclude "Vectorizing an unaligned
>> access" test for non-PowerPC arches.
>>
>>
>> Index: gcc/testsuite/gcc.dg/vect/vect-33.c
>> ===================================================================
>> --- gcc/testsuite/gcc.dg/vect/vect-33.c (revision 224490)
>> +++ gcc/testsuite/gcc.dg/vect/vect-33.c (working copy)
>> @@ -38,7 +38,7 @@ int main (void)
>>
>>
>> /* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect"
>} } */
>> -/* { dg-final { scan-tree-dump-times "Vectorizing an unaligned
>access" 0 "vect" { target { ! vect_hw_misalign } } } } */
>> +/* { dg-final { scan-tree-dump-times "Vectorizing an unaligned
>access" 0 "vect" { target { { ! powerpc*-*-* } || { ! vect_hw_misalign
>} } } } } */
>> /* { dg-final { scan-tree-dump "Alignment of access forced using
>peeling" "vect" { target vector_alignment_reachable } } } */
>> /* { dg-final { scan-tree-dump-times "Alignment of access forced
>using versioning" 1 "vect" { target { {! vector_alignment_reachable} &&
>{! vect_hw_misalign} } } } } */
>> /* { dg-final { cleanup-tree-dump "vect" } } */
>>
>>
prev parent reply other threads:[~2015-06-16 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 19:55 Bill Schmidt
2015-06-15 20:30 ` Bill Schmidt
2015-06-16 6:09 ` Richard Biener [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=5D62F220-B403-4F6D-B5CD-365CC85BE843@suse.de \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=wschmidt@linux.vnet.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).