Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/tests
History
rin 3353f76b9d Fix (a kind of) violation of strict aliasing rule. 
Due to the rule, "sin" and "sin6" can be treated as restrict pointers.
Compilers seem to be confused by structure copy for those pointed by
them before assignments.

For aarch64eb, GCC 9 and 10 compile t_tcp.c rev 1.11 into a code, where
fetch for "sin6->sin6_port" is preceding the structure copy "ss = bs".
This results in failure of connect(2) with EADDRNOOTAVAIL.
 		2021-11-08 10:57:09 +00:00
..
bin Add swab tests from RVP. 2021-10-08 14:45:07 +00:00
crypto
…
dev fix typos in word "successful". 2021-09-16 22:19:10 +00:00
fs With the recent "centralize vnode kevent handling" kevent(2) no 2021-10-30 09:53:47 +00:00
games
…
include
…
ipf
…
kernel Fix a regression introduced in kern_event.c,v 1.129 that would cause 2021-10-23 18:46:26 +00:00
lib Fix linking for multi-source file tests, the second part of the tuple 2021-11-07 18:05:36 +00:00
libexec Good bye oabi! Tested building earmv7hf. 2021-06-07 17:11:16 +00:00
modules
…
net Fix (a kind of) violation of strict aliasing rule. 2021-11-08 10:57:09 +00:00
rump Allow to set sanitizer flags for the rump build from the 2021-07-07 11:51:45 +00:00
sbin Delete trailing whitespace 2021-10-30 13:50:12 +00:00
share
…
sys s/existant/existent/ in comments and messages, plus few more similar fixes. 2021-09-03 22:33:17 +00:00
usr.bin fix various typos, mainly s/prefered/preferred/ 2021-11-07 20:31:09 +00:00
usr.sbin fix warnings 2021-09-01 06:12:50 +00:00
Makefile
…
Makefile.inc Allow to set sanitizer flags for the rump build from the 2021-07-07 11:51:45 +00:00
README
…
h_macros.h
…

README 

$NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho Exp $

When adding new tests, please try to follow the following conventions.

1. For library routines, including system calls, the directory structure of
   the tests should follow the directory structure of the real source tree.
   For instance, interfaces available via the C library should follow:

	src/lib/libc/gen -> src/tests/lib/libc/gen
	src/lib/libc/sys -> src/tests/lib/libc/sys
	...

2. Equivalently, all tests for userland utilities should try to follow their
   location in the source tree. If this can not be satisfied, the tests for
   a utility should be located under the directory to which the utility is
   installed. Thus, a test for env(1) should go to src/tests/usr.bin/env.
   Likewise, a test for tcpdump(8) should be in src/tests/usr.sbin/tcpdump,
   even though the source code for the program is located under src/external.

3. Otherwise use your own discretion.