[llvm-dev] lit conditional compilation/checking?
<Alexander G. Riccio> via llvm-dev
llvm-dev at lists.llvm.org
Thu Apr 14 14:42:53 PDT 2016
>
> Clang should be setting up the usual preprocessor defines based on the
> target.
>
placeholder text
It doesn't seem like that works as I'd expect: an #if defined(_WIN32)
didn't seem to fire on my local Windows machine. What #defines can I use?
Sincerely,
Alexander Riccio
--
"Change the world or go home."
about.me/ariccio
<http://about.me/ariccio>
If left to my own devices, I will build more.
⁂
On Wed, Apr 13, 2016 at 7:05 PM, Robinson, Paul <
Paul_Robinson at playstation.sony.com> wrote:
> Clang should be setting up the usual preprocessor defines based on the
> target. So, you can bracket chunks of C/C++ source in a lit test with #if
> to guard target-dependent stuff. Charles Li has been updating a bunch of
> tests to have sections guarded by tests on the value of __cplusplus, for
> example (e.g. see r266239).
>
> If you're asking about conditionally executing RUN lines, I don't think
> there's a way to do that; you'd need to split the new stuff into its own
> file and use REQUIRES to set the correct conditions.
>
> --paulr
>
>
>
> *From:* llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] *On Behalf Of *<Alexander
> G. Riccio> via llvm-dev
> *Sent:* Wednesday, April 13, 2016 1:56 PM
> *To:* llvm-dev
> *Subject:* [llvm-dev] lit conditional compilation/checking?
>
>
>
> How can I platform-conditionally compile/check sections of code with lit?
> Can I rely on preprocessor defines like _WIN32?
>
>
>
> Specifically, I'm adding new tests to existing lit tests, but the new
> tests should only be compiled and run on Windows.
>
>
>
>
> Sincerely,
> Alexander Riccio
> --
> "Change the world or go home."
>
> about.me/ariccio
>
>
> <http://about.me/ariccio>
>
> If left to my own devices, I will build more.
>
> ⁂
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160414/73f0d10d/attachment.html>
More information about the llvm-dev
mailing list