gpsd-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ✘64-bit time_t on glibc 2.34 and up


From: Gary E. Miller
Subject: Re: ✘64-bit time_t on glibc 2.34 and up
Date: Fri, 13 Jan 2023 16:41:56 -0800

Yo Greg!

On Fri, 13 Jan 2023 19:33:35 -0500
Greg Troxel <gdt@lexort.com> wrote:

> [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.

Interesting.  I see the glibc headers files use that notation.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

Attachment: pgp2fxajxE1fs.pgp
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]