Move t_mktime and t_strptime to their own ..../time/ subdirectory.

(Concurrence from christos@)

Remove bogus errno checks, mktime() (and timegm()) does not guarantee
to leave errno unaltered if there is no error. And does not.

While here, write -1 the same way everyone else does (not ~0, which
would not even be negative on a 1's complement host, if you can find one).

And while not needed for the test, but so that if checked, the result is
more likely to be what is anticipated, set tm_mday to an in-range value
in the mtime_negyear test (otherwise the correction results in the result
movng backwards to the last day of the previous month, which is the
end of Decemper, 1898, rather than the 1899 one would expect from year -1.)

Add a test case for the old NetBSD 2.0 era PR lib/28324.

ATF_REQUIRE_ERRNO() needs to be used with care:
- pass the expected errno to it, not "errno"
- make sure to have errno set already before invoking the macro, i.e.
do not use it to test errno changes as side effect of the asserted
expression

Spotted by mlelstv, makes the epoch tests correctly fail on amd64 as
well.

Add some tests for timegm(3) close to the epoch. In
particular, 1969-12-31 23:59:59 should convert to (time_t)-1
with errno = 0.

branches: 1.2.4;
Remove the following (literal) text in the TNF copyrights:

* This code is derived from software contributed to The NetBSD Foundation
* by
*

XXX: If these originated from you and you want your name to be mentioned,
please add it.

Move t_mktime and t_strptime to their own ..../time/ subdirectory.

(Concurrence from christos@)

t_strptime: fix typo in test description

strptime(3): Exercise some edge cases in the automatic tests.

Unfortunately, we can't quite use strptime as a black box to detect
the cases that triggered undefined behaviour, because strptime just
fails in that case anyway since the number that would go in .tm_year
is far out of the representable range.

PR lib/58041

branches: 1.15.4; 1.15.12;
use ATF_CHECK instead of ATF_REQUIRE
(continue on failure, to see the rest of the failures)

From Ngie Cooper in PR bin/51834

branches: 1.14.2;

The Zone test was obviously intended to test %Z rather than %z, otherwise
it would be (and has been) identical to the zone test, which would be a
pointless waste of time.

The military/nautical time zones were added following RFC 822 and RFC
2822 specifications. Unfortunately they are specified incorrectly in
RFC-822 and not very clearly in RFC 2822. RFC 1123 clearly states they
are specified incorrectly - counting the wrong way from UTC - in RFC
822. RFC 2822 just states they were implemented in a non-standard way.
Mea culpa for not noticing when originally implemented. Fix them so
the correct calculations are made.

merge more the tests

Account for J, fix %Z

tests for %Z

ISO 8601 and RFC 3339 specify that an offset can be up to 23:59 and
not 12:00 east/west. Just proves that one shouldn't use other
implementations as a canonical reference. Thanks to all who pointed
this out.

Additional tests for timezone offsets.

Add tests for %z

strptime now sets tm_yday

Add hour tests as a standalone test case.

Make century and year conversion tests a standalone test case rather than
part of the "common" test case.

Make seconds conversion tests a standalone test case rather than
part of the "common" test case.

Add more detail to test descriptions.

Move t_mktime and t_strptime to their own ..../time/ subdirectory.

(Concurrence from christos@)