This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH], PowerPC long double transition patches, v2, Patch #3 (use correct way to get the IEEE 128-bit complex type)
On Thu, Jun 21, 2018 at 10:43:16PM +0000, Joseph Myers wrote:
> On Thu, 21 Jun 2018, Segher Boessenkool wrote:
>
> > The comment doesn't make much sense. If long double is IBM, the long
> > double complex mode is ICmode, not KCmode. "To get the IEEE128 complex
> > type", perhaps? And can't you do _Complex __ieee128 or such?
>
> You can do _Complex _Float128, in C only, not C++ (which doesn't have the
> _Float128 keyword). _Complex can be used with keywords for type names,
> but not with a typedef name (built-in or otherwise, see discussion in bug
> 32187).
__ieee128 is a type, not a typedef:
lang_hooks.types.register_builtin_type (ieee128_float_type_node, "__ieee128");
(Or what am I missing? Or are we talking past eachother?)
Segher
- References:
- [PATCH], PowerPC long double transition patches, v2
- Re: [PATCH], PowerPC long double transition patches, v2, Patch #3 (use correct way to get the IEEE 128-bit complex type)
- Re: [PATCH], PowerPC long double transition patches, v2, Patch #3 (use correct way to get the IEEE 128-bit complex type)
- Re: [PATCH], PowerPC long double transition patches, v2, Patch #3 (use correct way to get the IEEE 128-bit complex type)