[PATCH] D29265: [legalize-types] Remove stale entries from SoftenedFloats.

[Chih-Hung Hsieh via Phabricator via llvm-commits]

chh added a comment.

Could you modify existing fp128 unit tests, especially those for Android target, to run with both current configuration and the "expensive checks". How do you enable the "expensive checks"?

I remember dealing with some differences between SoftenedFloats and ReplacedValues maps, when I twisted various configurations to get fp128 values not softened for some operators and saved in mmx registers. I am afraid that a lot of cases were not tested with the "expensive checks" enabled.


https://reviews.llvm.org/D29265