Bill Wendling ed91169004 The getDefaultSubtargetFeatures method of SubtargetFeature did actually return a ... string of features for that target. However LTO was using that string to pass into the "create target machine" stuff. That stuff needed the feature string to be in a particular form. In particular, it needed the CPU specified first and then the attributes. If there isn't a CPU specified, it required it to be blank -- e.g., ",+altivec". Yuck. Modify the getDefaultSubtargetFeatures method to be a non-static member function. For all attributes for a specific subtarget, it will add them in like normal. It will also take a CPU string so that it can satisfy this horrible syntax. llvm-svn: 103451		2010-05-11 00:30:02 +00:00
..
lto.cpp
lto.exports	Generalize the EXPORTED_SYMBOL_FILE concept in the Makefiles to work with	2010-04-15 20:54:25 +00:00
LTOCodeGenerator.cpp	The getDefaultSubtargetFeatures method of SubtargetFeature did actually return a	2010-05-11 00:30:02 +00:00
LTOCodeGenerator.h
LTOModule.cpp	The getDefaultSubtargetFeatures method of SubtargetFeature did actually return a	2010-05-11 00:30:02 +00:00
LTOModule.h
Makefile	Make the export files absolute paths, and change Makefile.rules	2010-04-15 23:08:00 +00:00