048488c0 cy March 22, 2021, 3:42 p.m.
40f41ece tuexen March 22, 2021, 2:58 p.m.
Ensure that the stack does not generate a DSACK block for user
data received on a SYN segment in SYN-SENT state.

Reviewed by:		rscheff
MFC after:		3 days
Differential Revision:	https://reviews.freebsd.org/D29376
Sponsored by:		Netflix, Inc.
f9a159da bapt March 22, 2021, 2:34 p.m.
a0409676 bapt March 22, 2021, 2:13 p.m.
3c319408 bapt March 22, 2021, 2:07 p.m.
64a790d2 emaste March 22, 2021, 1:34 p.m.
Sponsored by:	The FreeBSD Foundation
7f5693d0 arichardson March 22, 2021, 1:06 p.m.
I only tested the WARNS=6 change on AArch64 and AMD64, but this file has
unused functions for architectures with LDBL_PREC == 53.

While touching this file change the LDBL_PREC == 53 checks to i386 checks.
The long double tests should only be disabled for i386 (due to the rather
odd rounding mode that it uses) not all architectures where long double
is the same as double.

PR:		205449
Fixes:		87d65c747a43 ("lib/msun: Allow building tests with WARNS=6")
Reported by:	Jenkins
c8c62548 arichardson March 22, 2021, 11:55 a.m.
This warning is very rarely useful (inline is a hint and not mandatory).
This flag results in many warnings being printed when compiling C++
code that uses the standard library with GCC.

This flag was originally added in back in r94332 but the flag is a no-op
in Clang ("This diagnostic flag exists for GCC compatibility, and has no
effect in Clang"). Removing it should make the GCC build output slightly
more readable.

Reviewed By:	jrtc27, imp
Differential Revision: https://reviews.freebsd.org/D29235
6ccdee8a arichardson March 22, 2021, 11:55 a.m.
Output a hex dump of the current fenv and the expected value to allow
comparing them without having to resort to interactive use of GDB.
2b181156 arichardson March 22, 2021, 11:55 a.m.
If all the require variables (XCC/XCXX/XCPP/XLD) are already set in the
environment, we don't have to infer a default value for the cross toolchain
path. This avoids an additional `brew --prefix` call when building with
cheribuild (since it already sets all these variables).
2b9dbcd3 arichardson March 22, 2021, 11:55 a.m.
Some CPUs (e.g. AArch64 QEMU) cannot trap on floating point exceptions and
therefore ignore the writes to the floating point control register inside
feenableexcept(). If no exceptions are enabled after
feenableexcept(FE_ALL_EXCEPT), we can assume that the CPU does not
support exceptions and we can then skip the test.

Reviewed By:	dim
Differential Revision: https://reviews.freebsd.org/D29095
87d65c74 arichardson March 22, 2021, 11:55 a.m.
The only change needed is to mark a few variables as static.
b424e003 arichardson March 22, 2021, 11:55 a.m.
Also print the mismatched values when numbers compare not equal.

Reviewed By:	dim
Differential Revision: https://reviews.freebsd.org/D29091
b358534a arichardson March 22, 2021, 11:55 a.m.
These appears to have been resolved by compiling the test with -fno-builtin
and/or using a newer compiler.

PR:		208703
Reviewed By:	ngie
Differential Revision: https://reviews.freebsd.org/D28884
133bc645 arichardson March 22, 2021, 11:55 a.m.
This provides better error messages that just an assertion failure and
also makes it easier to mark individual tests as XFAIL.
It was also helpful when coming up with D28786 and D28787.

Differential Revision: https://reviews.freebsd.org/D28798