https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112606

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <ja...@gcc.gnu.org>:

https://gcc.gnu.org/g:58d5546af901364f85588fe668559d76f09e6df9

commit r14-6192-g58d5546af901364f85588fe668559d76f09e6df9
Author: Jakub Jelinek <ja...@redhat.com>
Date:   Tue Dec 5 21:39:31 2023 +0100

    rs6000: Canonicalize copysign (x, -1) back to -abs (x) in the backend
[PR112606]

    The middle-end has been changed quite recently to canonicalize
    -abs (x) to copysign (x, -1) rather than the other way around.
    While I agree with that at GIMPLE level, since it matches the GIMPLE
    goal of as few operations as possible for a canonical form (-abs (x)
    is 2 GIMPLE statements, copysign (x, -1) is just one), I must say
    I don't really like that being done on RTL as well (or at least
    not canonicalizing (COPYSIGN x, negative) back to (NEG (ABS x))),
    because on most targets most of floating point constants need to be loaded
    from memory, there are a few exceptions but -1 is often not one of them.

    Anyway, the following patch fixes the rs6000 regression caused by the
    change in GIMPLE canonicalization (i.e. the desirable one).  As rs6000
    clearly prefers -abs (x) form because it has a single instruction to do
    that while it also has copysign instruction, but that requires loading the
    -1 from memory, the following patch just ensures the copysign expander
    can actually see the floating point constant and in that case emits the
    -abs (x) code (or in the hypothetical case of copysign with non-negative
    constant abs (x) - but there copysign (x, 1) in GIMPLE is canonicalized
    to abs (x)), otherwise forces the operand to be the expected
gpc_reg_operand
    and does what it did before.

    2023-12-05  Jakub Jelinek  <ja...@redhat.com>

            PR target/112606
            * config/rs6000/rs6000.md (copysign<mode>3): Change predicate
            of the last argument from gpc_reg_operand to any_operand.  If
            operands[2] is CONST_DOUBLE, emit abs or neg abs depending on
            its sign, otherwise if it doesn't satisfy gpc_reg_operand,
            force it to REG using copy_to_mode_reg.

Reply via email to