[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ✘64-bit time_t on glibc 2.34 and up
From: |
Greg Troxel |
Subject: |
Re: ✘64-bit time_t on glibc 2.34 and up |
Date: |
Fri, 13 Jan 2023 19:33:35 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (berkeley-unix) |
[dropping ntpsec because they bounced my mail]
"Gary E. Miller" <gem@rellim.com> writes:
>> but int is ok in
>> practice, on ILP32. On IP16L32, it's not, but we aren't building for
>> PDP-11 any more :-)
>
> What is ILP32? Or IP16L32?
ILP32 means int, long and pointer are all 32 bits. Like the vax, and
i386.
LP64 means long/* are 64, and by implication int is 32. Like x86_64,
sparc64, aarch74
ILP64 means int is also 64. Like alpha.
IP16L32 I just made up; 16-bit ints and pointers, 32 longs. That's the
UNIX ABI on PDP-11.
- ✘64-bit time_t on glibc 2.34 and up, Gary E. Miller, 2023/01/12
- Re: ✘64-bit time_t on glibc 2.34 and up, Greg Troxel, 2023/01/13
- Re: ✘64-bit time_t on glibc 2.34 and up, Gary E. Miller, 2023/01/13
- Re: ✘64-bit time_t on glibc 2.34 and up, Greg Troxel, 2023/01/13
- Re: ✘64-bit time_t on glibc 2.34 and up, Greg Troxel, 2023/01/13
- Re: ✘64-bit time_t on glibc 2.34 and up, Gary E. Miller, 2023/01/13
- Re: ✘64-bit time_t on glibc 2.34 and up, Greg Troxel, 2023/01/14
- Re: ✘64-bit time_t on glibc 2.34 and up, Gary E. Miller, 2023/01/14
- Re: ✘64-bit time_t on glibc 2.34 and up, Gary E. Miller, 2023/01/13
- Re: ✘64-bit time_t on glibc 2.34 and up, Greg Troxel, 2023/01/14
- Re: ✘64-bit time_t on glibc 2.34 and up, Gary E. Miller, 2023/01/14
- Re: ✘64-bit time_t on glibc 2.34 and up, Greg Troxel, 2023/01/15