search for: aarno

...with any additional CFLAGS/CXXFLAGS/LDFLAGS)... Of course, if you need anything custom, there are likely examples in the test suite that you can use for guidance. Also, this may be of some help: https://llvm.org/docs/TestSuiteMakefileGuide.html On Tue, Jan 2, 2018 at 9:14 PM, Eli Davis <eli at aarno-labs.com> wrote: > Ah, thank you, that makes sense. > > Is there any chance you can point me toward some documentation for how to > add tests to the test-suite? I've found a fair bit on how to run the tests, > but nothing on how to add new ones. Is it just as simple as adding...

Ah, thank you, that makes sense. Is there any chance you can point me toward some documentation for how to add tests to the test-suite? I've found a fair bit on how to run the tests, but nothing on how to add new ones. Is it just as simple as adding testcase.c and testscase.reference_output in the appropriate directory? Thanks! On 01/02/2018 02:50 PM, Nemanja Ivanovic wrote: >

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/...

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 On 01/03/2018 11:17 PM, Sean Silva wrote: > Typically this would be tested alongside the runtime component in > compiler-rt. > For example, PGO instrumentation has its "end-to-end" tests in >

Typically this would be tested alongside the runtime component in compiler-rt. For example, PGO instrumentation has its "end-to-end" tests in https://github.com/llvm-mirror/compiler-rt/tree/master/test/profile -- Sean Silva On Tue, Jan 2, 2018 at 11:16 AM, Eli Davis via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hello! > > I am writing an instrumentation pass using

Typically the "end-to-end" test cases reside in `projects/test-suite`. All the test cases there build executable binaries from source, run those and compare the output (as well as the return code) to what's expected. You should probably put your test cases in there. Please note also that there are subcategories there - there are single source file and multiple source file programs.