diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2024-05-07 21:30:21 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2024-05-07 21:30:21 +0200 |
| commit | 28ee13db2e9d995bd3728c4ff3a3545e24b39cd2 (patch) | |
| tree | ae551eb6c017592229ea6c85e0b2bf6c9b904701 /gcc/cp/parser.cc | |
| parent | d4e25cf4f7c1f51a8824cc62bbb85a81a41b829a (diff) | |
| download | gcc-28ee13db2e9d995bd3728c4ff3a3545e24b39cd2.zip gcc-28ee13db2e9d995bd3728c4ff3a3545e24b39cd2.tar.gz gcc-28ee13db2e9d995bd3728c4ff3a3545e24b39cd2.tar.bz2 | |
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.
Diffstat (limited to 'gcc/cp/parser.cc')
0 files changed, 0 insertions, 0 deletions