This appears to be yet another case of IR1 transform stomping on VOPs. Disabling the TRUNCATE transform gives the desired code. *sigh*
Was it Paul who had the sketch for inhibiting transforms when we have applicable VOPs? What was the status of that? Should I back out the floating point truncate changes, which were a win only for case we could not implement using the straight-line version, or...?
This appears to be yet another case of IR1 transform stomping on VOPs. Disabling the TRUNCATE transform gives the desired code. *sigh*
Was it Paul who had the sketch for inhibiting transforms when we have applicable VOPs? What was the status of that? Should I back out the floating point truncate changes, which were a win only for case we could not implement using the straight-line version, or...?
(Context: https:/ /bugs.launchpad .net/bugs/ 489388)
Cheers,
-- Nikodemus