This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Testing patch to make FDO profile data tolerate more source changes
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: Neil Vachharajani <nvachhar at google dot com>
- Cc: gcc at gcc dot gnu dot org, Diego Novillo <dnovillo at google dot com>, jh at suse dot cz, nathan at codesourcery dot com
- Date: Mon, 30 Mar 2009 14:50:36 -0700
- Subject: Re: Testing patch to make FDO profile data tolerate more source changes
- References: <b3d309910903301353re2ffbb3p5d92cefd26e1f224@mail.gmail.com>
- Reply-to: janis187 at us dot ibm dot com
On Mon, 2009-03-30 at 13:53 -0700, Neil Vachharajani wrote:
> Hello,
>
> I'm working on a patch which makes FDO profile data more robust to
> source changes. Before I sent the patch to the list for review, I was
> wondering how to write a test for this situation. In particular, what
> I would like to have is two source files which are similar but not the
> same. The first should be compiled and run to generate profile data,
> and the generated .gcda file should be used to compile the second
> file. I wasn't quite sure how to do this within the DejaGNU framework
> and was wondering if anyone had some pointers.
Existing FDO tests use lib/profopt.exp via g++.dg/bprob/bprob.exp
and gcc.misc-tests/bprob.exp. You can copy those .exp files to
variants that use different versions of the source file for the
two compiles. Let me know if you have further questions.
Janis