This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Testing ICEs resulting from profile directed optimization
- From: "Paulo Matos" <pmatos at broadcom dot com>
- To: "Jan Hubicka" <hubicka at ucw dot cz>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Fri, 11 Oct 2013 08:23:50 +0000
- Subject: RE: Testing ICEs resulting from profile directed optimization
- Authentication-results: sourceware.org; auth=none
- References: <19EB96622A777C4AB91610E763265F462D8090 at SJEXCHMB14 dot corp dot ad dot broadcom dot com> <20131010162422 dot GB24619 at atrey dot karlin dot mff dot cuni dot cz>
> -----Original Message-----
> From: Jan Hubicka [mailto:hubicka@ucw.cz]
> Sent: 10 October 2013 17:24
> To: Paulo Matos
> Cc: gcc@gcc.gnu.org
> Subject: Re: Testing ICEs resulting from profile directed optimization
>
> > Hi,
> >
> > I have found an ICE reported as (PR 58682) and I have a fix.
> Cool :)
>
> > However the testcase involved:
> > * compiling a 5 .i files with -fprofile-generate=
> > * running the executable
> > * compiling the same 5 .i files with -fprofile-use=, and only then getting
> the ICE.
> >
> > Is there anything in the GCC testing framework that allows this kind of
> testing as opposed to the straightforward single test compilation?
>
> You probably only want to put those tests into gcc.dg/tree-prof directory.
> Those tests are run
> with FDO. You will need to convert them to .c files.
>
I have looked at the infrastructure and it seems it only supports single file tests.
I was not able to reduce the ICE to a single file. The reason for this is because I need to compile the project,
execute it and compile it again.
I could in theory simply add the gcda file plus the single .i (transformed into .c) that causes the ICE but
this would only work for the version of gcc that creates the gcda so it seems to be a no-go.
Any suggestions?
--
Paulo Matos