[lit] Fix setup of sanitizer environmentNot all options were propageted into tests.Reviewed By: ychenDifferential Revision: https://reviews.llvm.org/D122869
Use lit_config.substitute instead of foo % lit_config.params everywhereThis mechanically applies the same changes from D121427 everywhere.Differential Revision: https://reviews.llvm.org/D121746
Revert "Attempt to disable MLIR JIT tests on PowerPC to unbreak the bot"This reverts commit 652f4b5140e231b679564a86019307291f7bf7cc.Re-enable MLLIR JIT tests.The MLIR Bot was updated to export
Revert "Attempt to disable MLIR JIT tests on PowerPC to unbreak the bot"This reverts commit 652f4b5140e231b679564a86019307291f7bf7cc.Re-enable MLLIR JIT tests.The MLIR Bot was updated to export LD_LIBRARY_PATH=/usr/lib64, whichseem to fix this issue.
show more ...
Attempt to disable MLIR JIT tests on PowerPC to unbreak the botThis is until we figure how to turn on the large code size model.
[lit] Sort test start times based on prior test timing dataLit as it exists today has three hacks that allow users to run tests earlier:1) An entire test suite can set the `is_early` boolean.2)
[lit] Sort test start times based on prior test timing dataLit as it exists today has three hacks that allow users to run tests earlier:1) An entire test suite can set the `is_early` boolean.2) A very recently introduced "early_tests" feature.3) The `--incremental` flag forces failing tests to run first.All of these approaches have problems.1) The `is_early` feature was until very recently undocumented. Nevertheless it still lacks testing and is a imprecise way of optimizing test starting times.2) The `early_tests` feature requires manual updates and doesn't scale.3) `--incremental` is undocumented, untested, and it requires modifying the *source* file system by "touching" the file. This "touch" based approach is arguably a hack because it confuses editors (because it looks like the test was modified behind the back of the editor) and "touching" the test source file doesn't work if the test suite is read only from the perspective of `lit` (via advanced filesystem/build tricks).This patch attempts to simplify and address all of the above problems.This patch formalizes, documents, tests, and defaults lit to recording the execution time of tests and then reordering all tests during the next execution. By reordering the tests, high core count machines run faster, sometimes significantly so.This patch also always runs failing tests first, which is a positive user experience win for those that didn't know about the hidden `--incremental` flag.Finally, if users want, they can _optionally_ commit the test timing data (or a subset thereof) back to the repository to accelerate bots and first-time runs of the test suite.Reviewed By: jhenderson, ylnDifferential Revision: https://reviews.llvm.org/D98179
Support multi-configuration generators correctly in several config filesMulti-configuration generators (such as Visual Studio and Xcode) allow the specification of a build flavor at build time inst
Support multi-configuration generators correctly in several config filesMulti-configuration generators (such as Visual Studio and Xcode) allow the specification of a build flavor at build time instead of config time, so the lit configuration files need to support that - and they do for the most part. There are several places that had one of two issues (or both!):1) Paths had %(build_mode)s set up, but then not configured, resulting in values that would not work correctly e.g. D:/llvm-build/%(build_mode)s/bin/dsymutil.exe2) Paths did not have %(build_mode)s set up, but instead contained $(Configuration) (which is the value for Visual Studio at configuration time, for Xcode they would have had the equivalent) e.g. "D:/llvm-build/$(Configuration)/lib".This seems to indicate that we still have a lot of fragility in the configurations, but also that a number of these paths are never used (at least on Windows) since the errors appear to have been there a while.This patch fixes the configurations and it has been tested with Ninja and Visual Studio to generate the correct paths. We should consider removing some of these settings altogether.Reviewed By: JDevlieghere, mehdi_aminiDifferential Revision: https://reviews.llvm.org/D96427
Add build files and update README. * Add initial version of build files; * Update README with instructions to download and build MLIR from github;--PiperOrigin-RevId: 241102092