* 64-bit ptrdiff_t in ape
@ 2020-03-25 10:30 jamos
0 siblings, 0 replies; only message in thread
From: jamos @ 2020-03-25 10:30 UTC (permalink / raw)
To: 9front
Oh, so ptrdiff_t joined uintptr_t in being 64-bit
on APE architectures, while size_t is still 32-bit.
It seems plausible, as addresses are generally 64-bit,
so diffs might also be bigger than 32-bit, at least
in the future.
Still, it’s interesting which kinds of "assumptions"
Posix code sometimes makes, that breaks depending on
the size of this type? I mean an application that uses
these quite specific types, in contrast to 'ordinary
types' such as int*, long, long long etc., would really
pick the right type for the right situation, and it
would just work?
I am not questioning anything, I am just curious to
understand type sizes, and porting, better.
Jonas
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-03-25 10:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-25 10:30 64-bit ptrdiff_t in ape jamos
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).