https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109329
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #2)
> (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
That is IMHO not a bug, but expected behavior, that is how gcc behaves on tons
of other architectures. The ISA flags are additive to the -march or -mcpu
choice, if you ask for -mcpu=power4 -mvsx, you simply need to run the code on
Power4 CPU or newer which is backwards compatible with that, and need to have
the VSX ISA as well (so effectively Power7 then).
Users shouldn't be forced to use just -mcpu=, they can choose some CPU, or just
go with whatever default there is, but then they can add or take away from that
some ISAs.
