https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109329
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2024-08-14
CC| |linkw at gcc dot gnu.org,
| |meissner at gcc dot gnu.org
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #2 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Jeevitha from comment #1)
> This test case requires a Power7 or above due to the ieeelongdouble ABI.
> The test case includes "ppc_float128_sw", but this is not helpful. We can
> use the target check "ppc_ieee128_ok" to verify IEEE support.
It's "unhelpful" since the ppc_float128_sw test adds -mvsx to the test case
fragment and we currently have a bug in the rs6000 backend where -mvsx
incorrectly silently enables Power7 code generation, rather than flagging an
error on -mcpu=XXX compiles where XXX is older than Power7, making us execute
the test case when we shouldn't be. Mike has patches submitted and not yet
reviewed that is supposed to "fix" that.
That being said, I think ppc_ieee128_ok is still the correct test to use here,
since the test case is using -mabi=ieeelongdouble. That will correctly disable
the test on pre-Power7 cpus even today.
Yes, the test case only has complex ibmdoubledouble code usage, since it
explicitly uses -mabi=ieeelongdouble on the command line and when we process
options, we cannot know there is no actual ieee128 code usage, we have to flag
an error for pre-Power7 cpus. So Segher, I assume you mean these test cases
should be run on P7 and later compiles, but not earlier than Power7, correct?
