need to set BINDIR

Add interrupted I/O tests (from RVP)

Use -Wl,--no-fatal-warnings for the mktemp(3) test.

Move the test for mktemp(3) to the right place.

PR standards/49279 add tests for open_memstream, ported from OpenBSD

Since the mktemp test case uses mktemp, make linker warnings non-fatal.

new mktemp test

branches: 1.9.2;
add positional argument tests

branches: 1.8.2;
Naive tests for the naive putc(3) family.

Few unit tests for the fopen(3) family.

Couple of unit tests for fflush(3).

Split out 't_printf' and 't_scanf' from 't_format' to gain the common
"functional scope" for the test files.

Naive tests for clearerr(3).

Converted from the "PCCA" test suite by Stathis Kamperis.

Migrate a couple more tests to aft

Add testcase for PR/44113: printf(3) should ignore zero padding for
nan/inf.

add fmemopen(3) derrived from POSIX:2008.
libc minor bump.

tests/stdio: normalize whitespace

space before star

Make opts.cmd const char * rather than char * -- nothing ever modifies
the string it points to, it is never passed to a function not taking a
const char * arg, and this allows "" (or other literal strings if ever
needed) to be assigned to it - which should fix the build.

fixes from RVP

fix printf format strings

Add interrupted I/O tests (from RVP)

Add interrupted I/O tests (from RVP)

tests/stdio: on test failure, print more details

On amd64, the test stdio_intr_iofbf fails:

stdout: numbers.in...iw.ir.ir. OK
stderr: h_testnumbers: bad line 3914889

This information is not enough to get a complete picture of the
situation, so provide more details.

Add interrupted I/O tests (from RVP)

Naive tests for clearerr(3).

Converted from the "PCCA" test suite by Stathis Kamperis.

PR/59847: fflush(3) should not fail on read only file pointers

Couple of unit tests for fflush(3).

tests/stdio: normalize whitespace

Use intmax_t to printf an off_t

add more info to ease future debugging.

fix unused variable warnings

branches: 1.3.2; 1.3.8;
Requires stdint.h.

add Makefile.inc everywhere so that we can set WARNS=4 by default. Amazing
how many bugs this found :-)

add fmemopen(3) derrived from POSIX:2008.
libc minor bump.

Avoid undefined behavior in is_module_present()

t_fopen.c:339:18, member access within misaligned address 0x7f7ff7ebd004
for type 'modstat_t' (aka 'struct modstat') which requires 8 byte alignment

PR misc/54382: whenever open(2) is called with O_CREAT, make sure to
pass an open mode argument.

Add 2 new tests in t_fopen

Added:
- fopen_nullptr (without COMPAT_10)
- fopen_nullptr_compat10 (with COMPAT_10)

PR kern/53948

Reviewed by <mgorny>

branches: 1.5.4;
In the fopen_regular and fopen_symlink tests, when (that is, if) a
failure occurs, distinguish in the failure message the cases where the
open succeeded (and should not have), and where it failed, but not for
the expected reason (the "wrong errno" case not tested, would require
manufacturing a broken kernel...).

Add O_NOFOLLOW ('l' mode modifier) tests to the fopen_mode test case
(tests that are intended to open the file) and also add a few missing
commas which were causing a few of the sub-tests to be skipped, and
others to be not quite testing exactly what was intended.

add a symlink test

A test case may not assume opening /dev/tty does something sensible.

Add one more case. Also remove a double fclose(3) and do not
steal stderr(3) as atf(7) may use it in case of failures.

Few unit tests for the fopen(3) family.

Split out 't_printf' and 't_scanf' from 't_format' to gain the common
"functional scope" for the test files.

Fix the $NetBSD$ tag (missed the trailing $)

Migrate a few more tests from old regress style to atf

comment why vax is left out of all the fun

vax doesn't have ieee fp, so, don't try to test ieee fp on vax.

Add testcase for PR/44113: printf(3) should ignore zero padding for
nan/inf.

Naive tests for the naive putc(3) family.

Increase the estimate of disk space required for the test, as the old
estimate recently proved too optimistic on the amd64 testbed on b4.

Skip the test when there is insufficient disk space. Fixes PR misc/56324.

tests/stdio: disable flappy test for EINTR with _IOFBF for now

This case is currently not handled correctly by fwrite/fflush, which
makes the test fail sometimes. The tests for _IONBF and _IOLBF are
pretty stable though.

tests/stdio: use standard ATF tools for verifying the test output

In case of a test failure, this outputs a diff between the actual and
expected files.

Even with the smaller buffer size LMAX, the fully buffered test fails.
It does so after printing numbers up to 12773, which together take 65532
bytes. The next number, 12774, would cross the 65536 boundary, but
instead of that number, 12710730 was written.

tests/stdio: wrap test command with atf_check

Previously, the test output was:

FAILED: Test case body returned a non-ok exit code, but this is
not allowed

In many cases, the test now succeeds, but in some cases it fails:

h_testnumbers: bad line "1287185
", expected 12774

h_testnumbers: bad line "6186889
", expected 6154889

fixes from RVP

Add interrupted I/O tests (from RVP)

Move the test for mktemp(3) to the right place.

branches: 1.1.2; 1.1.8;
new mktemp test

tests/stdio: normalize whitespace

Add negative offset checks to fseeko

These were not strictly needed before, as lseek would error on negative
arguments, but having added open_memstream we have a virtual file pointer
that assumes that it gets sane values, so we get an assertion triggered
on a negative value. Best to check in one place rather than at all the
relevant points.

PR standards/49279 add tests for open_memstream, ported from OpenBSD

look at my index finger

branches: 1.3.2; 1.3.8;
Rename few test case names. No functional change.

Turn warns on for all tests and fix all the bugs.

branches: 1.1.4;
Migrate a couple more tests to aft

tests/lib/libc/stdio/t_printf: Fix sign error in ld128 case.

Also link back to where the test case came from.

tests/lib/libc/stdio/t_printf: Fix typo in ld128 case.

printf %La does not write the `L' suffix.

tests/lib/libc/stdio/t_printf: Fix another rounding error.

Noted by kre.

This doesn't break a passing test or fix a failed test, at least on
x86 -- our printf produces `0x1.533p+3' for the double case and
`0xa.99ap+0' for the long double case. But of the hexadecimal number
literals that that start with 0x5 having three hexadigits to the
right of the fractional point, 0x5.4cdp+1 closest to the IEEE 754
binary64, VAX D, x86 extended precision, and IEEE 754 binary128
floating-point numbers closest to 10.6.

The reason is that the number 10.6 (or the nearest floating-point
number in any format with enough precision) is:

101.0100 1100 1100|1100... * 2^1 = 0x5.4cc|c...p+1

If we round at the vertical bar to the _nearest_ output with three
hexadigits of precision, the result is:

101.0100 1100 1101 * 2^1 = 0x5.4cdp+1

Revert various broken changes to printf %La (hldtoa).

This reverts:

hdtoa.c 1.12 (PR/56247: Greg A. Woods: printf("%La", LDBL_MIN) dumps core)
hdtoa.c 1.11 (fix tyop)
hdtoa.c 1.10 (Via enh at google dot com in tech-userlevel. Fix handling of
EXT_FRAC{H,L}BITS (although we don't need to since we don't have them).)

The underlying motivation for this change was that when ld128 is
decomposed into 4x32 words, this hldtoa logic is broken.

But we don't decompose ld128 into 4x32 words; we decompose it into
6x64 words.

And the change, which was supposed to be a noop in our case of 2x64
words (or similar for x87 80-bit floating-point), broke it to the
point of causing buffer overruns (PR 56247) which when worked around
led to just incorrect output output (PR 56937).

If we want to make the #ifdefs for 4x32 words work, that's fine, but
we absolutely must have automatic test cases to detect this kind of
regression because %La formatting is extremely important for
diagnosing details of floating-point data since it doesn't involve
rounding in binary formats. For now I've added some trivial tests;
there is a more extensive test suite inside gdtoa that we need to
wire up before anyone tries any other shenanigans in this code.

PR lib/56937: printf(3) long double %a formatting is broken

tests/lib/libc/stdio/t_printf: Add another %La test.

This one was adapted from the screw case shown in

https://mail-index.netbsd.org/tech-userlevel/2020/04/11/msg012329.html

which wasn't broken in our libc, but which nevertheless prompted us
to commit a wrong and apparently untested patch that has rendered
printf %La broken for the last four years, which is a little
embarrassing. (The part of that patch that led to a buffer overrun
has been worked around, so now the output is just incorrect.)

PR lib/56937: printf(3) long double %a formatting is broken

tests/lib/libc/stdio/t_printf: Fix %a test the same way.

tests/lib/libc/stdio/t_printf: Fix %La test.

0xa.99ap+0 is closer to (long double)10.6 in x86 ld80 and in
binary128 (and possibly more formats, haven't verified).

tests/lib/libc/stdio/t_printf: Add a couple simple %La tests.

PR lib/56937: printf(3) long double %a formatting is broken

Fix the test for "inf" output, also include newline in printf format...

Add a test for PR/57250 from Havard Eidnes

branches: 1.8.34; 1.8.42;
Reduce the number of snprintf(3) invocations, as sparc/qemu timeouts.

Verify that PR lib/22019 is no longer an issue.

Move the references to PRs from code comments to the test description. Once
ATF has the ability to output the metadata in the HTML reports, it should be
easy to traverse between releng and gnats -reports via links.

Fix format strings to properly quote %.

add a test to verify that snprintf float does not leak.

add positional argument tests

branches: 1.2.2; 1.2.4;
Rename few test case names. No functional change.

Split out 't_printf' and 't_scanf' from 't_format' to gain the common
"functional scope" for the test files.

tests/stdio: normalize whitespace

Move the references to PRs from code comments to the test description. Once
ATF has the ability to output the metadata in the HTML reports, it should be
easy to traverse between releng and gnats -reports via links.

Fix format strings to properly quote %.

branches: 1.1.2; 1.1.4;
Split out 't_printf' and 't_scanf' from 't_format' to gain the common
"functional scope" for the test files.