[PATCH] [SimplifyCFG] Swap to using TargetTransformInfo for cost analysis.

Kristof Beyls kristof.beyls at arm.com
Mon Feb 9 09:39:40 PST 2015


I'm assuming that this patch should help to make sure vmin/vmax/fmin/fmax instructions gets produced for C code similar to
if (a<b) b=a;

If that is indeed one of the intents, it may be good to write a test to check that? After having quickly looked into existing regression tests, it seems there are plenty of tests to check correct MC-level handling of vmin/vmax/fmin/fmax instructions and also quite a lot of tests checking it gets generated when the operation is encoded as a select in llvm-ir, but I couldn't find a test that checks that a multi-basic-block representation of the operation is turned into an vmin/vmax/fmin/fmax.


REPOSITORY
  rL LLVM

http://reviews.llvm.org/D7506

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






More information about the llvm-commits mailing list