public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-7073] Fix expected output for s390 tests Date: Sat, 5 Feb 2022 17:28:12 +0000 (GMT) [thread overview] Message-ID: <20220205172812.EE0D8385843A@sourceware.org> (raw) https://gcc.gnu.org/g:f49b8d25b1ff96e9cd09326666cc510b3a3accde commit r12-7073-gf49b8d25b1ff96e9cd09326666cc510b3a3accde Author: Jeff Law <jeffreyalaw@gmail.com> Date: Sat Feb 5 12:17:56 2022 -0500 Fix expected output for s390 tests Recent changes in diagnostic outputs have been triggering failures on the s390 testsuite. In particular, capitalization changed in one diagnostic and the range representation changed in another. This patch makes the obvious updates to the s390 testsuite. gcc/testsuite * gcc.target/s390/20150826-1.c: Update expected output. * gcc.target/s390/zvector/imm-range-error-1.c: Likewise. Diff: --- gcc/testsuite/gcc.target/s390/20150826-1.c | 2 +- gcc/testsuite/gcc.target/s390/zvector/imm-range-error-1.c | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/gcc/testsuite/gcc.target/s390/20150826-1.c b/gcc/testsuite/gcc.target/s390/20150826-1.c index 1567ced42e1..67a285ff367 100644 --- a/gcc/testsuite/gcc.target/s390/20150826-1.c +++ b/gcc/testsuite/gcc.target/s390/20150826-1.c @@ -9,4 +9,4 @@ int foo(void) { char b[100]; return bar(b); -} /* { dg-warning "An unconditional trap is added" } */ +} /* { dg-warning "an unconditional trap is added" } */ diff --git a/gcc/testsuite/gcc.target/s390/zvector/imm-range-error-1.c b/gcc/testsuite/gcc.target/s390/zvector/imm-range-error-1.c index 021c8d297d2..a627b5408dc 100644 --- a/gcc/testsuite/gcc.target/s390/zvector/imm-range-error-1.c +++ b/gcc/testsuite/gcc.target/s390/zvector/imm-range-error-1.c @@ -17,10 +17,10 @@ main () triggered from s390_expand_builtin. Otherwise they would come from the parser already preventing other errors from showing up. */ - __builtin_s390_vrepb (q, 17); /* { dg-error "constant argument 2 for builtin '__builtin_s390_vrepb' is out of range \\(0..15\\)" } */ - __builtin_s390_vreph (h, 8); /* { dg-error "constant argument 2 for builtin '__builtin_s390_vreph' is out of range \\(0..7\\)" } */ - __builtin_s390_vrepf (s, 4); /* { dg-error "constant argument 2 for builtin '__builtin_s390_vrepf' is out of range \\(0..3\\)" } */ - __builtin_s390_vrepg (d, 2); /* { dg-error "constant argument 2 for builtin '__builtin_s390_vrepg' is out of range \\(0..1\\)" } */ + __builtin_s390_vrepb (q, 17); /* { dg-error "constant argument 2 for builtin '__builtin_s390_vrepb' is out of range \\(0-15\\)" } */ + __builtin_s390_vreph (h, 8); /* { dg-error "constant argument 2 for builtin '__builtin_s390_vreph' is out of range \\(0-7\\)" } */ + __builtin_s390_vrepf (s, 4); /* { dg-error "constant argument 2 for builtin '__builtin_s390_vrepf' is out of range \\(0-3\\)" } */ + __builtin_s390_vrepg (d, 2); /* { dg-error "constant argument 2 for builtin '__builtin_s390_vrepg' is out of range \\(0-1\\)" } */ - __builtin_s390_vpdi (d, d, 4); /* { dg-error "constant argument 3 for builtin '__builtin_s390_vpdi' is out of range \\(0..3\\)" } */ + __builtin_s390_vpdi (d, d, 4); /* { dg-error "constant argument 3 for builtin '__builtin_s390_vpdi' is out of range \\(0-3\\)" } */ }
reply other threads:[~2022-02-05 17:28 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=20220205172812.EE0D8385843A@sourceware.org \ --to=law@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: linkBe 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).