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
..
Interpreter	eliminate the Type::getDescription() method, using "<<" instead. This	2011-06-18 21:18:23 +00:00
JIT	ExecutionEngine: move createJIT() definition (v2)	2011-05-13 22:02:53 +00:00
MCJIT	Avoid a Twine that referenced a tmp (which proceded to go out of scope before	2011-05-19 00:45:05 +00:00
RuntimeDyld	Be a bit more permissive about symbols we don't understand. Just skip them	2011-05-13 23:11:30 +00:00
CMakeLists.txt	ExecutionEngine: fix JIT/MCJIT selectTarget() duplication (v2)	2011-05-13 21:36:16 +00:00
ExecutionEngine.cpp	ExecutionEngine: move createJIT() definition (v2)	2011-05-13 22:02:53 +00:00
ExecutionEngineBindings.cpp
Makefile
TargetSelect.cpp	Fix the ridiculous SubtargetFeatures API where it implicitly expects CPU name to	2011-06-30 01:53:36 +00:00