Liste des Groupes | Revenir à c arch |
kegs@provalid.com (Kent Dickey) writes:Until the advent of int32_t the only way to get a known 32-bit containerBringing it back to "architecture" Like Anton Ertl has said, LP64 for>
C/C++ is a mistake. It should always have been ILP64, and this nonsense
would go away. Any new architecture should make C ILP64 (looking at you
RISC-V, missing yet another opportunity to not make the same mistakes as
everyone else).
We now have had more than 30 years of catering for this mistake by
everyone involved. Given their goals, I think that RISC-V made the
right choice for int in their ABI, even if it was the original choice
by the MIPS and Alpha people that they follow, like everyone else, was
wrong.
That being said, one option would be to introduce another ABI and API
with 64-bit int (and maybe 32-bit long short int), and programmers
could choose whether to program for the ILP API, or the int=int32_t
API. Would the ILP API/ABI fare better then x32? I doubt it, even
though I would support it. This ship probably has sailed.
>
- anton
Les messages affichés proviennent d'usenet.