[PATCH, C++] Fix PR63366: __complex not equivalent to __complex double in C++
Thomas Preud'homme
thomas.preudhomme@arm.com
Wed Oct 29 14:39:00 GMT 2014
> From: Nathan Sidwell [mailto:nathanmsidwell@gmail.com] On Behalf Of
> Nathan Sidwell
>
> It's not an error to omit it for complex - but of course means something
> different. IMHO it would be confusing to set type to integer_type_node
> when
> that's definitely wrong. But then setting 'defaulted_int' when that's not
> the
> case is also confusing.
Oh in that case the patch is incomplete. Currently a complex alone gives
an error at compilation which is why I added -fpermissive to the testcase.
The patch don't change this behavior.
Best regards,
Thomas
More information about the Gcc-patches
mailing list