This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Does "complex xxx" work?
On Sat, 21 Jun 2003, H. J. Lu wrote:
> If I added
>
> record_builtin_type (RID_LONG, "__int64",
> long_integer_type_node);
>
> should the parser accept "unsigned __int64"? If somehow I make it
No, at least not properly in all cases, because the parser knows which
keywords are type specifiers; __int64 seems to be designed as a keyword,
and implementing it as something else isn't a robust solution. I don't
believe we want to add this extra keyword to GCC. If the Intel compiler
makes __int64 a type compatible with long long and unsigned __int64
compatible with unsigned long long, or if it makes them compatible with
long / unsigned long (with 64-bit long), then just use the compatible
types. If it is a type incompatible with all standard types of that size,
more consideration may be needed.
--
Joseph S. Myers
jsm28@cam.ac.uk