From: Jakub Jelinek <jakub@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: gcc-patches@gcc.gnu.org, "Martin Liška" <mliska@suse.cz>
Subject: [committed] testsuite: Fix up pr103456.c testcase [PR103456]
Date: Fri, 3 Dec 2021 12:13:37 +0100 [thread overview]
Message-ID: <20211203111337.GP2646553@tucnak> (raw)
In-Reply-To: <20211201083159.4044250-1-siddhesh@gotplt.org>
On Wed, Dec 01, 2021 at 02:01:59PM +0530, Siddhesh Poyarekar wrote:
> PR tree-optimization/103456
> * gcc.dg/ubsan/pr103456.c: New test.
ubsan.exp cycles through torture options, and that includes
-O2 -flto -fno-fat-lto-objects. But with those options
tree dump scans don't work for post-IPA passes, for dg-do
compile tests nothing after IPA is done. So we get an
unresolved testcase:
gcc.dg/ubsan/pr103456.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects : dump file does not exist
UNRESOLVED: gcc.dg/ubsan/pr103456.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects scan-tree-dump-not objsz1 "maximum object size 0"
Fixed by adding -ffat-lto-objects so that we perform the post-IPA
passes.
Tested on x86_64-linux, committed to trunk as obvious.
2021-12-03 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/103456
* gcc.dg/ubsan/pr103456.c: Add -ffat-lto-objects to dg-options.
--- gcc/testsuite/gcc.dg/ubsan/pr103456.c.jj 2021-12-01 10:03:55.404029919 +0100
+++ gcc/testsuite/gcc.dg/ubsan/pr103456.c 2021-12-03 12:06:57.613750230 +0100
@@ -1,6 +1,6 @@
/* PR tree-optimization/103456 */
/* { dg-do compile } */
-/* { dg-options "-fsanitize=undefined -O -fdump-tree-objsz" } */
+/* { dg-options "-fsanitize=undefined -O -fdump-tree-objsz -ffat-lto-objects" } */
static char *multilib_options = "m64/m32";
Jakub
prev parent reply other threads:[~2021-12-03 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 4:17 [PATCH] tree-optimization/103456 - Record only successes from object_sizes_set Siddhesh Poyarekar
2021-12-01 7:18 ` Jakub Jelinek
2021-12-01 8:31 ` [COMMITTED] " Siddhesh Poyarekar
2021-12-03 11:13 ` Jakub Jelinek [this message]
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=20211203111337.GP2646553@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=siddhesh@gotplt.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).