public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] testsuite: vect: update unaligned message
Date: Wed, 27 Apr 2022 21:29:43 +0000 (GMT)	[thread overview]
Message-ID: <20220427212943.B4E29385741C@sourceware.org> (raw)

https://gcc.gnu.org/g:1d7cfa78fa0ff1796c7da6f498257ec305b04bf8

commit 1d7cfa78fa0ff1796c7da6f498257ec305b04bf8
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Wed Apr 27 18:23:01 2022 -0300

    testsuite: vect: update unaligned message
    
    gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c covers ppc variants
    that accept and reject misaligned accesses.  The message that it
    expects for rejection was removed in the gcc-11 development cycle by
    commit r11-1969.  The patch adjusted multiple tests to use the message
    introduced in r11-1945, but missed this one.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c: Update
            the expected message for the case in which unaligned accesses
            are not allowed.

Diff:
---
 gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c b/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c
index 72b4930d9bb..c57f065cccd 100644
--- a/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c
+++ b/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c
@@ -46,5 +46,5 @@ int main (void)
   return main1 ();
 } 
 
-/* { dg-final { scan-tree-dump-times "not vectorized: unsupported unaligned store" 1 "vect" { target { ! vect_hw_misalign } } } } */
+/* { dg-final { scan-tree-dump-times "unsupported unaligned access" 1 "vect" { target { ! vect_hw_misalign } } } } */
 /* { dg-final { scan-tree-dump-times "vectorized 1 loops" 0 "vect" { target { ! vect_hw_misalign } } } } */


                 reply	other threads:[~2022-04-27 21:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220427212943.B4E29385741C@sourceware.org \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).