Re: C time_t 2038 problem s-os_lib.ads

[Joakim Strandberg <joakimds@kth.se>]

torsdag 23 september 2021 kl. 17:01:04 UTC+2 skrev m8il...@gmail.com:
> On Thursday, September 23, 2021 at 2:26:11 PM UTC, Jeffrey R. Carter wrote: 
> > On 9/23/21 12:42 PM, Kevin Chadwick wrote: 
> > > I have noticed that C time_t appears to be Long_integer in Gnat s-os_lib.ads. 
> > > 
> > > Just wondering if it should be 64bit long long as OpenBSD has already moved to long long? 
> > GNAT defines 
> > 
> > type Long_Integer is range -(2 **63) .. +(2 **63 - 1); 
> > for Long_Integer'Size use 64; 
> >
> I see, thank you. 
> 
> GPS doesn't seem to jump to declaration for Long_Integer and grep hasn't turned it up, 
> so I will just take your word for it.

Well, yes Long_Integer is 64-bits, but long long in cpp is 128 bits which sounds like a discrepancy to me. On OpenBSD it indicates C time_t should be changed from Long_Integer to somethinge else that is 128-bits.  All packages in Ada has "with Standard; use Standard;" which brings Integer etc. into scope. Long_Integer should be defined in the Standard package. Under help in GPS it should be possible to find the Standard package.

Best regards,
Joakim