Matthias Braun 255e441613 X86: Do not return invalid cost for fp16 conversion (#114128) ...

Returning invalid instruction costs when converting from/to fp16 in
`X86TTIImpl::getCastInstrCost` when there is no hardware support
available was triggering asserts. This changes the code to return a
large (arbitrary) number to model the fact that libcalls are used to
implement the conversion.

This also simplifies the code by only reporting costs for the scalar
fp16 conversion; vectorized costs being left to the fallback assuming
scalarization.

This is a follow-up to assertion issues reported for the changes in
#113195

2024-10-29 17:16:17 -07:00

336 KiB

Raw Blame History

View Raw