Evan Cheng 276365dd4b Fix the ridiculous SubtargetFeatures API where it implicitly expects CPU name to ... be the first encoded as the first feature. It then uses the CPU name to look up features / scheduling itineray even though clients know full well the CPU name being used to query these properties. The fix is to just have the clients explictly pass the CPU name! git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@134127 91177308-0d34-0410-b5e6-96231b3b80d8		2011-06-30 01:53:36 +00:00
..
bugpoint
buildit
count
crosstool
emacs
FileCheck
FileUpdate
fpcmp
git
jedit
kate
KillTheDoctor
lint
lit	lit support for REQUIRES: asserts.	2011-06-22 23:23:19 +00:00
llvm-lit
Misc
not
PerfectShuffle
release
TableGen	Fix the ridiculous SubtargetFeatures API where it implicitly expects CPU name to	2011-06-30 01:53:36 +00:00
Target/ARM
unittest
valgrind
vim
cgiplotNLT.pl
check-each-file
codegen-diff
countloc.sh
DSAclean.py
DSAextract.py
findmisopt
findoptdiff
findsym.pl
GenLibDeps.pl
GetRepositoryPath
GetSourceVersion
getsrcs.sh
importNLT.pl
llvm-native-gcc
llvm-native-gxx
llvm.grm	Add a new function attribute, nonlazybind, which inhibits lazy-loading	2011-06-15 20:36:13 +00:00
llvmbuild
llvmdo
llvmgrep
Makefile
makellvm
NewNightlyTest.pl
NightlyTest.gnuplot
NightlyTestTemplate.html
NLT.schema
parseNLT.pl
plotNLT.pl
profile.pl
show-diagnostics
test_debuginfo.pl
UpdateCMakeLists.pl
webNLT.pl