[llvm-dev] Testing "normal" cross-compilers versus GPU backends

[Robinson, Paul via llvm-dev]

Modifying lit itself to support running a "generic" test multiple times, iterating through some specified set of triples, seems like a rather more ambitious feature than I'm willing to sign up for.  You guys want such a thing, knock yourselves out.

But does this suggest a groundswell of support for configurations where the default triple's target is NOT included in the build?  And having the LLVM tests tolerate that configuration?  That patch I have 90% done, and it seems to work okay; my only real objection is that it endorses a pretty counter-intuitive kind of configuration.

(And if an iterate-through-triples patch supersedes what I did, that's fine too—but my immediate goal is to re-enable cross-compiler testing of these generic tests, which currently isn't happening at all.)
--paulr

From: David Blaikie [mailto:dblaikie at gmail.com]
Sent: Friday, September 04, 2015 8:51 AM
To: James Y Knight
Cc: Robinson, Paul; Robinson, Paul via llvm-dev
Subject: Re: [llvm-dev] Testing "normal" cross-compilers versus GPU backends



On Fri, Sep 4, 2015 at 7:37 AM, James Y Knight via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
Relatedly, I'd really like it if there was some way to run all of those generic tests for *more* than just the default triple. It's quite unfortunate that you cannot easily run, say, the DebugInfo tests for both X86 and Sparc at one go.

It'd be great if there was some sort of 'list of triples to run the generic tests on' build option. If that existed, it'd solve both my wish (to be able to run the tests for multiple such triples -- ideally I think it'd *default* to running them on each configured-in target!),

(making it the default would make check-all a bit slow, I would imagine - but yes, having an easy option "ninja check-all-llvm-targets" or something like that could be handy (maybe this could generalize to Clang tests too, not sure - many of them don't have a fixed triple and it'd be nice to be able to reproduce failures from an apple buildbot on linux, etc))

and Mehdi's desire to not run them at all.

Just by setting the set of targets to empty? Makes sense.

_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150904/3b13d556/attachment.html>