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] fix array element count Date: Wed, 15 Mar 2023 23:30:18 +0000 (GMT) [thread overview] Message-ID: <20230315233018.E7D913857BB3@sourceware.org> (raw) https://gcc.gnu.org/g:681630ac000c0660e6c72f2f0a1a6f925f1c0021 commit 681630ac000c0660e6c72f2f0a1a6f925f1c0021 Author: Alexandre Oliva <oliva@adacore.com> Date: Wed Mar 15 07:55:04 2023 -0300 [testsuite] fix array element count This test is similar to pr103116-1.c, but instead of writing to 4*COUNT elements of x, it writes to 8*COUNT elements, but the definition of x seems to have been adjusted along with the loop. Fix the array size so that it doesn't scribble over unrelated statically-allocated objects. for gcc/testsuite/ChangeLog * gcc.dg/vect/pr103116-2.c (x): Fix array size. Diff: --- gcc/testsuite/gcc.dg/vect/pr103116-2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.dg/vect/pr103116-2.c b/gcc/testsuite/gcc.dg/vect/pr103116-2.c index 2f4ed0f404c..aa9797a9407 100644 --- a/gcc/testsuite/gcc.dg/vect/pr103116-2.c +++ b/gcc/testsuite/gcc.dg/vect/pr103116-2.c @@ -31,7 +31,7 @@ loop (TYPE *restrict x, TYPE *restrict y) } } -TYPE x[COUNT * 4]; +TYPE x[COUNT * 8]; int main (void)
next reply other threads:[~2023-03-15 23:30 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-15 23:30 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-03-16 1:44 Alexandre Oliva 2023-03-15 14:06 Alexandre Oliva
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=20230315233018.E7D913857BB3@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: 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).