https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108068
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This was added for PR44683 and I bet the reason it uses real_zerop is that we
don't have other APIs, or at least ones that work on floating point types for
it.
I suppose short term we could use TREE_CODE (op0) == REAL_CST && TREE_REAL_CST
(op0).cl != rvc_zero but the question is what to do for COMPLEX_CSTs and
VECTOR_CSTs.
I bet for COMPLEX_CSTs, we shouldn't infer anything if signed zeros are allowed
and either real or imag or both parts are zero, for VECTOR_CSTs similarly if
any elt is zero.
For SSA_NAMEs eventually we could ask frange...
