[llvm-commits] [llvm] r79615 - in /llvm/trunk/test/Analysis/Profiling: ./ 2009-08-21-irregular-loop.ll 2009-08-21-only-one-block.ll 2009-08-21-several-blocks.ll dg.exp

Daniel Dunbar daniel at zuster.org
Tue Aug 25 11:20:53 PDT 2009

On Tue, Aug 25, 2009 at 10:56 AM, Chris Lattner<clattner at apple.com> wrote:
> On Aug 25, 2009, at 10:41 AM, Daniel Dunbar wrote:
>> On Tue, Aug 25, 2009 at 5:59 AM, Andreas
>> Neustifter<e0325716 at student.tuwien.ac.at> wrote:
>>>> We should solve the problem that this requires the JIT, though. A
>>>> simple first option is to disable the test if there is no JIT support.
>>>> A slightly better one would be to run it using the .bca version of the
>>>> profiling information, but that of course requires that the user
>>>> configure with llvm-gcc support.
>>> What is the easiest way to check if JIT is supported on a give platform
>>> during the tests?
>> Unfortunately I don't think we have one. Someone should step in and
>> correct me if I am wrong!
>> It should be straightforward albeit annoying to this to the
>> XFAIL/XTARGET mechanisms we use, for example (implemented by
>> test/lib/llvm.exp, in conjunction with the Makefile setting fields in
>> the site.exp).
> I think that llvm-config either knows or could know:
> my $TARGET_HAS_JIT      = q{1};
> Maybe it should get a new command line option?

There is still some work to suck this into DejaGNU so it knows not to
run the test if the JIT isn't present. Or did you have something else
in mind?

 - Daniel

More information about the llvm-commits mailing list