[PATCH] Initial instrumentation based PGO implementation

[Eric Christopher]

I don't think we should have any executable tests in the front end at all.
I think the easiest way here would be to check in an input file alongside
the test file similar to how the Object tests work (an Inputs directory).

Thoughts?

On Tue Dec 17 2013 at 12:19:59 PM, Justin Bogner <mail at justinbogner.com>
wrote:

> Justin Bogner <mail at justinbogner.com> writes:
> >> +// RUN: %clangxx %s -o %t1 -fprofile-instr-generate
> >> +// RUN: mkdir -p %tdir && cd %tdir && %t1
> >>
> >> This is going to fail on any platform that doesn't have native codegen
> >> enabled by default.
> >
> > Hmm. Is there a REQUIRES or something I can use to conditionally enable
> > them then? I'm guessing if we don't have native codegen I can't do
> > something tricky like generate IR and run it with lli or something
> > either.
>
> This seems to be "REQUIRES: native". I'll add that to both tests.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20131219/e085c77f/attachment.html>