This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Year 2000/2037 compliance

> Does anybody know definitely whether egcs and the libraries that come with
> it are year 2000 or even year 2037-compliant?

Jeff, maybe this needs to go into the FAQ, because this question is going
to be asked with increasing levels of panic as the big date gets closer.

Fortunately, egcs and the libraries do virtually no date manipulation.

gcc itself only deals with the year at one point: the expansion of __DATE__
in the preprocessor.  The code is written in a Y2K-correct way, though it
relies on a correct localtime() routine from the C library.  ctime() is
used at several points in writing out profiling or debug information.

As for the libraries, libio and libstdc++ don't deal with time at all; the
only use of time is in the Fortran runtime library, which is just wrappers
around the C library functions.  Again, provided that there are correct
localtime(), gmtime(), and ctime() functions in the C library, egcs would
appear to have no problems until 2037.

> I just got an survey from HP regarding HP-UX, and they say you have to
> patch the libc even on systems up to 10.20. So I started wondering about
> egcs..

egcs does not include a C library, so you need to check with whoever
provides the C library on your system.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]