..
analyze
Make sure to print a stack trace whenever an error signal is delivered
2004-02-19 20:33:00 +00:00
bugpoint
After reducing a miscompiled program down to the functions which are being
2004-03-14 22:08:00 +00:00
extract
Make sure to print a stack trace whenever an error signal is delivered to
2004-02-19 20:32:39 +00:00
gccas
Turn on argument promotion in gccas. This can give us substantially better
2004-03-13 21:38:35 +00:00
gccld
Run the new pass in gccld now that it passes all tests
2004-03-07 22:12:40 +00:00
llc
SparcV8 removed until it grows up becomes a mature backend.
2004-03-11 18:16:33 +00:00
llee
lli
Great renaming part II: Sparc --> SparcV9 (also includes command-line options and Makefiles)
2004-02-25 19:08:12 +00:00
llvm-ar
Make sure to print a stack trace whenever an error signal is delivered to the
2004-02-19 20:32:12 +00:00
llvm-as
Make sure to print a stack trace whenever an error signal is delivered to the
2004-02-19 20:32:12 +00:00
llvm-db
Great renaming part II: Sparc --> SparcV9 (also includes command-line options and Makefiles)
2004-02-25 19:08:12 +00:00
llvm-dis
Make sure to print a stack trace whenever an error signal is delivered to the
2004-02-19 20:32:12 +00:00
llvm-extract
Make sure to print a stack trace whenever an error signal is delivered to
2004-02-19 20:32:39 +00:00
llvm-link
Make sure to print a stack trace whenever an error signal is delivered to the
2004-02-19 20:32:12 +00:00
llvm-nm
Make sure to print a stack trace whenever an error signal is delivered to the
2004-02-19 20:32:12 +00:00
llvm-prof
Annotate functions with edge counts as well, if they are available.
2004-03-08 20:04:32 +00:00
opt
Make sure to print a stack trace whenever an error signal is delivered to the
2004-02-19 20:32:12 +00:00
Makefile