Evan Cheng 034261674b 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! llvm-svn: 134127		2011-06-30 01:53:36 +00:00
..
llvm	Fix the ridiculous SubtargetFeatures API where it implicitly expects CPU name to	2011-06-30 01:53:36 +00:00
llvm-c	Cast unused parameter to void.	2011-06-04 16:00:19 +00:00