[llvm-commits] [cfe-commits] The AArch64 LLVM (& Clang) target
Renato Golin
renato.golin at linaro.org
Tue Jan 8 01:30:34 PST 2013
On 7 January 2013 22:15, Tim Northover <t.p.northover at gmail.com> wrote:
> I personally favour: build an AArch64-native Clang on x86; dispatch an
> llvm-regression run and a clang-regression run to models (each takes
> ~5 hours).
>
This is more or less what we have for ARM 32-bits anyway. A nightly
check-all would already be of great help, though it'd be hard to count it
as "don't break" target with that turnaround.
> Alternatives might involve the llvm testsuite (> 1 day, probably not
> useful). Or SPEC runs (similar times, but even more difficult for
> others to investigate when it breaks; possible licensing issues
> anyway).
>
With LNT you can run the whole simple tests or individual tests, so if you
need a more fine grained control over what gets tested, you can.
I'd think that time is more important than coverage at this stage, so if
you can set up a number of tests with enough coverage that would only take
a few hours, you could go for that. When you get a faster model, or an FPGA
materialises you increase the number of tests, and so on, up to the full
test-suite.
At least that would keep the "don't break" status because you could fix and
test quickly afterwards...
cheers,
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130108/1aeccd21/attachment.html>
More information about the llvm-commits
mailing list