summaryrefslogtreecommitdiff
path: root/tools/bugpoint
diff options
context:
space:
mode:
authorSylvestre Ledru <sylvestre@debian.org>2012-07-23 08:51:15 +0000
committerSylvestre Ledru <sylvestre@debian.org>2012-07-23 08:51:15 +0000
commitc8e41c591741b3da1077f7000274ad040bef8002 (patch)
treede48920d877025af8ab8945b1dfc33404a31ffad /tools/bugpoint
parented1a335ece5c83230af662580e69008ed6fcca17 (diff)
downloadllvm-c8e41c591741b3da1077f7000274ad040bef8002.tar.gz
llvm-c8e41c591741b3da1077f7000274ad040bef8002.tar.bz2
llvm-c8e41c591741b3da1077f7000274ad040bef8002.tar.xz
Fix a typo (the the => the)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@160621 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'tools/bugpoint')
-rw-r--r--tools/bugpoint/BugDriver.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/bugpoint/BugDriver.cpp b/tools/bugpoint/BugDriver.cpp
index 6b219bf085..21636eabab 100644
--- a/tools/bugpoint/BugDriver.cpp
+++ b/tools/bugpoint/BugDriver.cpp
@@ -156,7 +156,7 @@ bool BugDriver::run(std::string &ErrMsg) {
// If we're not running as a child, the first thing that we must do is
// determine what the problem is. Does the optimization series crash the
// compiler, or does it produce illegal code? We make the top-level
- // decision by trying to run all of the passes on the the input program,
+ // decision by trying to run all of the passes on the input program,
// which should generate a bitcode file. If it does generate a bitcode
// file, then we know the compiler didn't crash, so try to diagnose a
// miscompilation.