Introduction and 64 bit time_t
Corinna Vinschen
vinschen@redhat.com
Wed Aug 9 15:51:00 GMT 2017
On Aug 9 13:47, Philipp.Trommler@preh.de wrote:
> Am Mittwoch, den 09.08.2017, 14:35 +0200 schrieb Corinna Vinschen:
>
> [snip]
>
> > I'd prefer to use the type long on LP64 systems, but long long should
> > work fine for all 32 bit systems (baring 32 bit Cygwin).
> >
> > However, a developer might want to design an embedded system still
> > using
> > a 32 bit time_t for the time being, so there should be some build-
> > time
> > switch for this case. We're talking about a 21 year timeframe, which
> > may still be more than enough for some systems.
>
> So we can agree on a build-time switch like --enable-long-long-time-t
What about --enable-32bit-time_t or something like that? By default
time_t should default to long on targets with sizeof(long)==8 and to
long long on targets with sizeof(long)==4.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/newlib/attachments/20170809/877452c5/attachment.sig>
More information about the Newlib
mailing list