ctype(3): New environment variable LIBC_ALLOWCTYPEABUSE.

If set, this does not force the ctype(3) functions to crash when
passed invalid inputs -- instead, they will return nonsense results,
and possibly print warnings to stderr, as is their right in
implementing undefined behaviour.

The nature of the nonsense results is unspecified. Currently, is*()
will always return true (even if that leads to mutually contradictory
conclusions, like isalpha and isdigit, or isgraph and isblank), and
tolower/toupper() will always return EOF. But perhaps in the future
the results may be randomized.

This way, if an application like firefox crashes on ctype abuse, you
can opt to accept the consequences of nonsense results instead by
running `env LIBC_ALLOWCTYPEABUSE= firefox' until the application is
fixed.

PR lib/58208: ctype(3) provides poor runtime feedback of abuse

branches: 1.60.2;
Add basic tests for timespec_get(3), timespec_getres(3)

PR standards/58608

ctype(3): Disable guard page in static libc.

Adding the guard page may have overflown several small installation
media. Let's try to keep this case small.

Update the tests to detect the cases where we will be running against
a libc without a guard page on the LC_CTYPE=C tables, and skip
testing abuse detection when it would rely on the guard page.

PR lib/58208: ctype(3) provides poor runtime feedback of abuse

t_ctype: New test for ctype(3) functions/macros.

PR lib/58208: ctype(3) provides poor runtime feedback of abuse

execve(2), posix_spawn(2): Add test case for an embarrassing bug.

PR kern/58091: after fork/execve or posix_spawn, parent kill(child,
SIGTERM) has race condition making it unreliable

arc4random(3): Add automatic tests.

This verifies that:
- arc4random zeroes its state and reseeds itself on fork
- arc4random reseeds itself on entropy consolidation (e.g., VM clone)
- arc4random falls back to global state if it can't allocate local
state because address space limits cause mmap to fail

NOTE: This adds a new libc symbol __arc4random_global, but it's in
the reserved namespace and only used by t_arc4random, so no libc
minor bump.

PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM
fork

branches: 1.55.2; 1.55.4;
libc: Reintroduce getentropy.

This was introduced two years ago when the getrandom/getentropy API
question was still open, and removed because the discussion was
ongoing. Now getentropy is more widely adopted and soon to be in
POSIX. So reintroduce the symbol into libc since we'll be keeping it
anyway. Discussion of details of the semantics, as interpreted by
NetBSD, is ongoing, but the symbol needs to get in before the
netbsd-10 branch. The draft POSIX text is
(https://www.opengroup.org/austin/docs/austin_1110.pdf):

SYNOPSIS
#include <unistd.h>

int getentropy(void *buffer, size_t length);

DESCRIPTION
The getentropy() function shall write length bytes of data
starting at the location pointed to by buffer. The output
shall be unpredictable high quality random data, generated by
a cryptographically secure pseudo-random number
generator. The maximum permitted value for the length
argument is given by the {GETENTROPY_MAX} symbolic constant
defined in <limits.h>.

RETURN VALUES
Upon successful completion, getentropy() shall return 0;
otherwise, -1 shall be retunred and errno set to indicate the
error.

ERRORS
The getentropy() function shall fail if:

[EINVAL] The value of length is greater than
{GETENTROPY_MAX}.

The getentropy() function may fail if:

[ENOSYS] The system does not provide the necessary
source of entropy.

RATIONALE
The getentropy() function is not a cancellation point.

Minor changes from the previous introduction of getentropy into libc:

- Return EINVAL, not EIO, on buflen > 256.
- Define GETENTROPY_MAX in limits.h.

The declaration of getentropy in unistd.h and definition of
GETENTROPY_MAX in limits.h are currently conditional on
_NETBSD_SOURCE. When the next revision of POSIX is finalized, we can
expose them also under _POSIX_C_SOURCE > 20yymmL as usual -- and this
can be done as a pullup without breaking existing compiled programs.

Update t_siginfo.c build rules

Add logic for MKSANITIZER/MKLIBCSANITIZER checks.

-frounding-math is gcc specific, help clang builds

PR/54000: Andreag Gustafsson: Compile the rounding test with
-fround-math since with gcc-7, the default mode ignores fenv settings
(the same effect can be achieved with -O0 :-)

https://gcc.gnu.org/wiki/FloatingPointMath

branches: 1.51.12;
remove exect, it will not be fixed and it will be removed.

branches: 1.50.2;
Attach t_exect to ATF tests and distribution

Add missing SIGTRAP handler. Assert there that the signal is SIGTRAP as
expected and si_code TRAP_TRACE.

This test will break on some ports that have dummy or incomplete
implementation of exect(2).

This test works on amd64 correctly.

Sponsored by <The NetBSD Foundation>

branches: 1.49.2;
Add __TEST_FENV

Put have fenv elsewhere.

Sync list of fenv enabled architectures again (PR 48633), this time for mips
addition.

While PR 48633 is not properly fixed, keep the additional lists of
fenv-enabled architectures in sync.

Build t_fpgetmask/t_fpgetround for aarch64 since they are now in libc

Enable fenv for arm

Do not set HAVE_FENV for arm as long as it misses feenableexcept().

Use the same condition for HAVE_FENV

Changes to existing files to enable building AARCH64 userland.
evbarm64-el
This is clang only. While gcc4.8 supports aarch64, no netbsd support has
been written for aarch64 with gcc4.8.

Minimal execve(2) ATF test.

branches: 1.39.2;
Add test for uint64 to real long double conversion.

Convert old src/regress/timer&waiter tests to ATF

branches: 1.37.2;
Do not re-add -mieee option on alpha, it's already set by default.

Add a case for PR lib/41558. It is unclear whether this is a bug, but at
least it is documented now. Probably it would be better to follow Linux,
where the test case does not fail.

Add few basic tests for realpath(3).

Move posix_spawn tests to lib/libc/gen/posix_spawn - they test both libc
and kernel, but that is an implementation detail unrelated to the tests
themselfs.
Ok: releng

Few naive checks for cpuset(3) and ftok(3).

Few naive checks for time(3).

branches: 1.31.2;
Make the rounding test work properly, and actually test the rounding modes.

Move duplicate ldexp(3) test out from the tests/libc.

Move the tests/libc/ieeefp to tests/libc/gen to match the structure of libc.
Also rename the test files to gain functional scope.

Move 't_glob_star' to 't_glob' for glob(3).

Move 't_syslog_pthread' to 't_syslog' for consistency with libc.

Test that assert(3) works.

Test also setdomainname(3).

Few naive tests for sethostname(3).

branches: 1.23.2;
Few naive tests for pause(3).

Few basic tests for closefrom(3).

Try to mirror the real source with the test directory structure (otherwise
the latter carries a risk of becoming a difficult mess to manage.)

Few fundamental consistency checks for alarm(2).

Test nice(3) also with threads.

A naive test case for getcwd(3).

Add simple test cases for ttyname(3), strtod(3), and getgrent(3).

Few simple tests for nice(3).

Sort.

Add a naive test case for raise(3).

Continuing the (re)organization of the lib/libc atf regression tests

One more reference to HAVE_SIGINFO bites the dust

Build t_ldexp test always. The test itself determines if it is running
on an unsupported platform (vax) and exits.

Fix name of t_ldexp test from previous

Don't build ldexp tests on vax

Migrate the ldexp test to atf

Migrate the remaining libc/gen tests to atf

Correctly added the conditional part, but now need to remove the original
unconditional part.

Don't include the siginfo tests unless we actually have siginfo ability!

Move the siginfo tests from regress to atf. While here, add a new test
for PR/43655.

XXX The sigchild_dump test currently fails when execute under atf-run.
XXX It does not fail when executed directly from the shell, so there's
XXX something in atf that prevents the child process from dumping.

Migrate a couple more tests from the old regress structure to atf

Add an isolated test case for PR lib/44248.

Add tests for GLOB_STAR