From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: hubicka@ucw.cz
Cc: ro@CeBiTec.Uni-Bielefeld.DE, developer@sandoe-acoustics.co.uk,
hubicka@ucw.cz, hp@axis.com, gcc-patches@gcc.gnu.org
Subject: Re: [RFA:] fix breakage with "Update testsuite to run with slim LTO"
Date: Fri, 21 Oct 2011 17:40:00 -0000 [thread overview]
Message-ID: <201110211620.p9LGK2HU026848@ignucius.se.axis.com> (raw)
In-Reply-To: <20111021154414.GC18476@atrey.karlin.mff.cuni.cz> (message from Jan Hubicka on Fri, 21 Oct 2011 17:44:15 +0200)
> Date: Fri, 21 Oct 2011 17:44:15 +0200
> From: Jan Hubicka <hubicka@ucw.cz>
> I also noticed that tests scanning output of late optimization passes are
> now getting UNRESOLVED state with slim LTO. We don't really lose coverage
> here because we test fat LTO with the other compilation, but probably easiest
> is to enfore fat LTO all the time.
>
> Does the following seem resonable?
>
> Honza
>
> * gcc.dg/torture/pta-ptrarith-1.c: Force fat LTO.
> * gcc.dg/torture/pta-ptrarith-2.c: Likewise.
> * gcc.dg/torture/pr23821.c: Likewise.
> * gcc.dg/torture/pta-ptrarith-3.c: Likewise.
> * gcc.dg/torture/pr45704.c: Likewise.
> * gcc.dg/torture/pr50472.c: Likewise.
> * gcc.dg/torture/ipa-pta-1.c: Likewise.
> * gcc.dg/torture/pta-callused-1.c: Likewise.
> * gcc.dg/torture/pr39074-2.c: Likewise.
> * gcc.dg/torture/pr39074.c: Likewise.
> * gcc.dg/torture/pr42898-2.c: Likewise.
> * gcc.dg/torture/pr42898.c: Likewise.
> * gcc.dg/torture/pta-escape-1.c: Likewise.
> * gcc.dg/torture/ssa-pta-fn-1.c: Likewise.
Meh... Please no, this was the kind of scatter-patches my patch
aimed to avoid... for example, easy to miss some tests.
Instead, on top of my patch, just copy the
scan-assembler_required_options proc to a
scan-tree-dump_required_options. ...no wait, should forcing
fat-lto be done for all tree-dumps? If only for a subset of
tree-dumps augment the *_required_options proc API to take
arguments that let you check for that.
brgds, H-P
next prev parent reply other threads:[~2011-10-21 16:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 17:54 Update testsuite to run with slim LTO Jan Hubicka
2011-09-30 14:56 ` Diego Novillo
2011-10-20 19:34 ` Breakage with "Update testsuite to run with slim LTO" Hans-Peter Nilsson
2011-10-20 19:53 ` Andi Kleen
2011-10-21 0:39 ` Jan Hubicka
2011-10-21 5:22 ` [RFA:] fix breakage " Hans-Peter Nilsson
2011-10-21 9:58 ` Jan Hubicka
2011-10-21 12:23 ` Iain Sandoe
2011-10-21 12:35 ` Rainer Orth
2011-10-21 16:20 ` Jan Hubicka
2011-10-21 17:40 ` Hans-Peter Nilsson [this message]
2011-10-21 18:52 ` Jan Hubicka
2011-10-21 19:56 ` Hans-Peter Nilsson
2011-10-24 12:08 ` Richard Guenther
2011-10-28 14:59 ` ping: [RFA:] testsuite infrastructure for options implied by dg-final methods Hans-Peter Nilsson
2011-11-04 13:56 ` ping*2: " Hans-Peter Nilsson
2011-11-04 17:05 ` Mike Stump
2011-11-04 17:54 ` Hans-Peter Nilsson
2011-11-04 18:14 ` Mike Stump
2011-11-04 18:16 ` Hans-Peter Nilsson
2023-05-03 11:16 ` Let each 'lto_init' determine the default 'LTO_OPTIONS', and 'torture-init' the 'LTO_TORTURE_OPTIONS' (was: Update testsuite to run with slim LTO) Thomas Schwinge
2023-05-03 11:46 ` Richard Biener
2023-05-09 7:32 ` Christophe Lyon
2023-05-09 9:00 ` Testsuite: Add missing 'torture-init'/'torture-finish' around 'LTO_TORTURE_OPTIONS' usage (was: Let each 'lto_init' determine the default 'LTO_OPTIONS', and 'torture-init' the 'LTO_TORTURE_OPTIONS') Thomas Schwinge
2023-05-09 15:17 ` Christophe Lyon
2023-05-09 19:14 ` Christophe Lyon
2023-05-10 7:51 ` Testsuite: Add 'torture-init-done', and use it to conditionalize implicit 'torture-init' (was: Testsuite: Add missing 'torture-init'/'torture-finish' around 'LTO_TORTURE_OPTIONS' usage (was: Let each 'lto_init' determine the default 'LTO_OPTIONS', and 'torture-init' the 'LTO_TORTURE_OPTIONS')) Thomas Schwinge
2023-05-10 13:42 ` Christophe Lyon
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=201110211620.p9LGK2HU026848@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=developer@sandoe-acoustics.co.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=hubicka@ucw.cz \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).