[PATCH] Have a way to let fast-isel handle normally optimized library functions

[reed kotler]

It seems from this history of this problem that we could just delete the 
code for all targets that my patch works around.

It seems it was just a bandaid on another problem that was better solved 
by just adding a virtual method in fast-isel
for handling intrinsics.

Now that that is there, any intrinsic that a given port does not want to 
handle will get handled by reverting
to non fast-isel.


http://reviews.llvm.org/D7397

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/