[llvm-dev] Testing End-To-End Functionality of Specific Optimization
Sean Silva via llvm-dev
llvm-dev at lists.llvm.org
Thu Jan 4 12:00:24 PST 2018
On Thu, Jan 4, 2018 at 8:14 AM, Eli Davis <eli at aarno-labs.com> wrote:
> Ah, that makes a lot of sense. Thank you! Do you have any tips (or points
> to documentation) for how to run compiler-rt tests? Just invoking llvm-lit
> doesn't seem to work
They should run as part of check-all when you have compiler-rt checked out
in llvm/projects/ (or the equivalent with the monorepo setup, which I think
is just setting the appropriate LLVM_EXTERNAL_*_SOURCE_DIR cmake variable).
I forget, but I'd be surprised if there isn't a "check-compiler-rt" or
similar. I've also used llvm-lit in the past (look at what
check-compiler-rt does; I think it just calls llvm-lit).
-- Sean Silva
> On 01/03/2018 11:17 PM, Sean Silva wrote:
> Typically this would be tested alongside the runtime component in
> For example, PGO instrumentation has its "end-to-end" tests in
> -- Sean Silva
> On Tue, Jan 2, 2018 at 11:16 AM, Eli Davis via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>> I am writing an instrumentation pass using LLVM. I have unit tests using
>> llvm-lit in the style of the tests in llvm/test to make sure the IR changes
>> show up in the correct place. I would also like to have some end-to-end
>> tests that start from a .c file, compile the program, run it, and check the
>> I imagine I could do this as a test in the same style, but I'm wondering
>> if that's the llvm-correct way of doing it. Can anyone advise?
>> Thank you!
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev