public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6471] testsuite: Skip gcc.dg/ipa/pr77653.c for CRIS Date: Sat, 4 Mar 2023 00:55:54 +0000 (GMT) [thread overview] Message-ID: <20230304005554.68E463858C74@sourceware.org> (raw) https://gcc.gnu.org/g:53940eee08957b8b72ee70f57770398009e19c21 commit r13-6471-g53940eee08957b8b72ee70f57770398009e19c21 Author: Hans-Peter Nilsson <hp@axis.com> Date: Fri Mar 3 17:49:01 2023 +0100 testsuite: Skip gcc.dg/ipa/pr77653.c for CRIS CRIS defines DATA_ALIGNMENT such that alignment can be applied differently to different data of the same type, when "references to it must bind to the current definition" (varasm.cc:align_variable). Here, it means that more alignment is then applied to g, but not f, so the test-case fails because another message is emitted than the expected: a same-alignment test dominates the not-discardable test, and we get "Not unifying; original and alias have incompatible alignments" rather than "Not unifying; alias cannot be created; target is discardable". Because this DATA_ALIGNMENT behavior for CRIS depends on target options, and this test is already artificial by the use of -fcommon, better skip it. * gcc.dg/ipa/pr77653.c: Skip for cris-*-*. Diff: --- gcc/testsuite/gcc.dg/ipa/pr77653.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/gcc.dg/ipa/pr77653.c b/gcc/testsuite/gcc.dg/ipa/pr77653.c index 2fddb7eab54..16df3fff6a4 100644 --- a/gcc/testsuite/gcc.dg/ipa/pr77653.c +++ b/gcc/testsuite/gcc.dg/ipa/pr77653.c @@ -1,5 +1,6 @@ /* { dg-require-alias "" } */ /* { dg-options "-O2 -fcommon -fdump-ipa-icf-details" } */ +/* { dg-skip-if "Can align g more than f" { cris-*-* } } */ int a, b, c, d, e, h, i, j, k, l; const int f;
reply other threads:[~2023-03-04 0:55 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=20230304005554.68E463858C74@sourceware.org \ --to=hp@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).