This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC/CFT] auto-wipe dump files [was: Re: [committed] Fix up bb-slp-31.c testcase]
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Bernhard Reutner-Fischer <rep dot dot dot nop at gmail dot com>
- Cc: Mike Stump <mikestump at comcast dot net>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Janis Johnson <janis_johnson at mentor dot com>
- Date: Thu, 31 Oct 2013 09:39:11 +0100
- Subject: Re: [RFC/CFT] auto-wipe dump files [was: Re: [committed] Fix up bb-slp-31.c testcase]
- Authentication-results: sourceware.org; auth=none
- References: <20131030094133 dot GA22154 at nbbrfq dot cc dot univie dot ac dot at> <5256BA07-2A04-4601-9523-76EFBF61E434 at comcast dot net> <CAC1BbcR7Ry8tFgGi3zKeRj=mAuxipt1Y+4XjF4jmSquCvn02cw at mail dot gmail dot com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Oct 31, 2013 at 09:34:41AM +0100, Bernhard Reutner-Fischer wrote:
> The cleanup routine would currently run 7 regexes on the incoming
> compiler-flags which is supposedly pretty fast.
> But yes, we could as well key off scan-dump. If we do that, i'd
> suggest to simply wipe all potential dumps, regardless of the "family"
> etc, like:
> "$ltrans\[0-9\]\[0-9\]\[0-9\][itr].*"
> What do you think?
Many tests (e.g. in gcc.dg/vect/) pass -fdump-* flags and require cleanups,
even if they don't have any scan directives.
Jakub