[Bug middle-end/114907] __trunchfbf2 should be renamed to __extendhfbf2

["cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

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

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

https://gcc.gnu.org/g:28ee13db2e9d995bd3728c4ff3a3545e24b39cd2

commit r15-303-g28ee13db2e9d995bd3728c4ff3a3545e24b39cd2
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue May 7 21:30:21 2024 +0200

    expansion: Use __trunchfbf2 calls rather than __extendhfbf2 [PR114907]

    The HF and BF modes have the same size/precision and neither is
    a subset nor superset of the other.
    So, using either __extendhfbf2 or __trunchfbf2 is weird.
    The expansion apparently emits __extendhfbf2, but on the libgcc side
    we apparently have __trunchfbf2 implemented.

    I think it is easier to switch to using what is available rather than
    adding new entrypoints to libgcc, even alias, because this is backportable.

    2024-05-07  Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/114907
            * expr.cc (convert_mode_scalar): Use trunc_optab rather than
            sext_optab for HF->BF conversions.
            * optabs-libfuncs.cc (gen_trunc_conv_libfunc): Likewise.

            * gcc.dg/pr114907.c: New test.