[ia64-abi] Issue reminder

[Cary Coutant]

>I also believe that the intent of __int64 is that it was
>just a nomenclature convenience for 64 bit integers, just
>like __int128 is for 128 bit integers.  Since the document
>is really describing binary representations, there is no
>requirement that there be anything like these names accepted
>as keywords (or predefined macros) in any compiler.
>
>As such, there's no issue about use of __int64 in source
>code.  If implementations choose to provide such a name, I'm
>confident that they'll "do it right".
>
>The same argument applies to __float80 and __float128.

Dave is right -- __int64, __int128, __float80, and __float128 are just 
notational conveniences for the core conventions document, which doesn't 
go so far as to specify what long, long long, and long double are.

An ABI document is expected to specify the standard types, so these "__" 
types aren't necessary in the ABI. Once the ABI has mapped a standard 
type to a hardware representation, the conventions document then provides 
the conventions for that type.

I'd be amenable to clarifying the core conventions document to this 
effect.

-cary