https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112993
Bug ID: 112993
Summary: rs6000: Rework precision for 128bit float types and
modes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: build, ice-checking, ice-on-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: linkw at gcc dot gnu.org
CC: amacleod at redhat dot com, andy at gwentswordclub dot
co.uk,
bergner at gcc dot gnu.org, linkw at gcc dot gnu.org,
meissner at gcc dot gnu.org, segher at gcc dot gnu.org,
seurer at gcc dot gnu.org, tschwinge at gcc dot gnu.org
Depends on: 112788
Target Milestone: ---
Host: powerpc64le-linux-gnu
Target: powerpc64le-linux-gnu
Build: powerpc64le-linux-gnu
+++ This bug was initially created as a clone of Bug #112788 +++
As PR112788 shows and the review comments from Andrew and Jakub at
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/640342.html, we should
get rid of the workaround for PR112788 from GCC 15+.
This PR is filed for tracking this, we would expect that the precision for
those types and modes are all 128 bit, also TFmode becomes one macro
conditionally defined as IFmode or KFmode.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112788
[Bug 112788] [14 regression] ICEs in fold_range, at range-op.cc:206 after
r14-5972-gea19de921b01a6
