public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-3959] testsuite/102517 - fix FAIL of gcc.dg/pr78408-1.c with OImode availability Date: Wed, 29 Sep 2021 12:35:24 +0000 (GMT) [thread overview] Message-ID: <20210929123524.1B8FB3858404@sourceware.org> (raw) https://gcc.gnu.org/g:b34fa88becb6367229074f25ef9e2de6f4594b58 commit r12-3959-gb34fa88becb6367229074f25ef9e2de6f4594b58 Author: Richard Biener <rguenther@suse.de> Date: Wed Sep 29 14:32:32 2021 +0200 testsuite/102517 - fix FAIL of gcc.dg/pr78408-1.c with OImode availability This fixes the testcase which looks for variants of memcpy after memset folding which is disturbed when we expand the memcpy inline earlier which in fact performs the desired optimization but makes the dump file not match. For the ease of testing the following adjusts the smaller structure size to be no longer power-of-two which avoids the inline expansion. 2021-09-29 Richard Biener <rguenther@suse.de> PR testsuite/102517 * gcc.dg/pr78408-1.c: Make S not power-of-two size. Diff: --- gcc/testsuite/gcc.dg/pr78408-1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.dg/pr78408-1.c b/gcc/testsuite/gcc.dg/pr78408-1.c index 94e2090b374..dc9870ac6af 100644 --- a/gcc/testsuite/gcc.dg/pr78408-1.c +++ b/gcc/testsuite/gcc.dg/pr78408-1.c @@ -3,7 +3,7 @@ /* { dg-options "-O2 -fdump-tree-fab1-details" } */ /* { dg-final { scan-tree-dump-times "after previous" 17 "fab1" } } */ -struct S { char a[32]; }; +struct S { char a[33]; }; struct T { char a[65536]; }; void bar (int, struct S *, struct S *, struct T *, struct T *); void baz (char *, char *);
reply other threads:[~2021-09-29 12:35 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=20210929123524.1B8FB3858404@sourceware.org \ --to=rguenth@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).