2002-11-21 06:30:02 +08:00
|
|
|
; Test that bugpoint can narrow down the testcase to the important function
|
|
|
|
|
;
|
[bugpoint] Find 'opt', etc., in bugpoint directory
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
2018-12-10 08:56:13 +08:00
|
|
|
; RUN: bugpoint -load %llvmshlibdir/BugpointPasses%shlibext %s -output-prefix %t -bugpoint-crashcalls -silence-passes > /dev/null
|
2019-05-17 14:41:04 +08:00
|
|
|
; REQUIRES: plugins
|
2002-11-21 06:30:02 +08:00
|
|
|
|
2007-03-20 02:08:42 +08:00
|
|
|
define i32 @foo() { ret i32 1 }
|
2002-11-21 06:30:02 +08:00
|
|
|
|
2007-03-20 02:08:42 +08:00
|
|
|
define i32 @test() {
|
|
|
|
|
call i32 @test()
|
|
|
|
|
ret i32 %1
|
2002-11-21 06:30:02 +08:00
|
|
|
}
|
|
|
|
|
|
2007-03-20 02:08:42 +08:00
|
|
|
define i32 @bar() { ret i32 2 }
|
