| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | [Bugpoint] Only run plugins tests if plugins are enabled | Petr Hosek | 2019-05-17 | 1 | -1/+1 |
| | | | | | | | | | This is a followup to r360991 which applies the same logic to LLVM. Differential Revision: https://reviews.llvm.org/D62050 llvm-svn: 360993 | ||||
| * | [bugpoint] Find 'opt', etc., in bugpoint directory | Brian Gesiak | 2018-12-10 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: When bugpoint attempts to find the other executables it needs to run, such as `opt` or `clang`, it tries searching the user's PATH. However, in many cases, the 'bugpoint' executable is part of an LLVM build, and the 'opt' executable it's looking for is in that same directory. Many LLVM tools handle this case by using the `Paths` parameter of `llvm::sys::findProgramByName`, passing the parent path of the currently running executable. Do this same thing for bugpoint. However, to preserve the current behavior exactly, first search the user's PATH, and then search for 'opt' in the directory containing 'bugpoint'. Test Plan: `check-llvm`. Many of the existing bugpoint tests no longer need to use the `--opt-command` option as a result of these changes. Reviewers: MatzeB, silvas, davide Reviewed By: MatzeB, davide Subscribers: davide, llvm-commits Differential Revision: https://reviews.llvm.org/D54884 llvm-svn: 348734 | ||||
| * | [bugpoint] Avoid noisy errors by passing a valid opt to tests | Vedant Kumar | 2018-02-09 | 1 | -1/+1 |
| | | | | | | | | If the tests don't use the in-tree opt, we're liable to see some silly error messages due to the version mismatch (missing flags, etc). llvm-svn: 324703 | ||||
| * | [IR/Verifier] List the CU we weren't able to find in `llvm.dbg.cu`. | Davide Italiano | 2017-02-20 | 1 | -1/+1 |
| | | | | | llvm-svn: 295678 | ||||
| * | Disable fatal errors in the Verifier instantiated by bugpoint's crash | Adrian Prantl | 2016-10-18 | 1 | -0/+22 |
| debugger. When bugpoint hacks at a testcase it may at one point create illegal debug info metadata that won't even pass the Verifier. A bugpoint *driver* built with assertions should not assert on it, but reject the malformed intermediate step and continue to do its job. llvm-svn: 284490 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|