This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/32187] Complex __float128 is rejected
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 19 Aug 2016 17:51:38 +0000
- Subject: [Bug target/32187] Complex __float128 is rejected
- Authentication-results: sourceware.org; auth=none
- Auto-submitted: auto-generated
- References: <bug-32187-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32187
--- Comment #12 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
You can now use _Complex _Float128. Given that, it's not obvious that
_Complex __float128, with the legacy __float128 type name, should be
supported (although not supporting that means also not supporting _Complex
__ibm128 for powerpc64le; both are built-in typedefs, and no _Float*
keyword can be used for __ibm128).
_Float128 isn't supported for C++, although there's the argument that
there std::complex<__float128> is the thing support should be added /
enabled for, rather than adding to the support for C-style complex types
in C++.