Dmitry Vyukov ecb386fe6f sys: check that target consts are defined ... Currently when we get target consts with target.ConstMap["name"] during target initialization, we just get 0 for missing consts. This is error-prone as we can mis-type a const, or a const may be undefined only on some archs (as we have common unix code shared between several OSes). Check that all the consts are actually defined. The check detects several violations, to fix them: 1. move mremap to linux as it's only defined on linux 2. move S_IFMT to openbsd, as it's only defined and used on openbsd 3. define missing MAP_ANONYMOUS for freebsd and netbsd 4. fix extract for netbsd		2018-10-19 19:11:22 +01:00
..
akaros	sys: check that target consts are defined	2018-10-19 19:11:22 +01:00
android	sys/linux: add ion and ashmem devices support	2018-01-09 21:24:28 +01:00
freebsd	sys: check that target consts are defined	2018-10-19 19:11:22 +01:00
fuchsia	Update fidlgen to keep current with upstream.	2018-10-10 12:00:14 +02:00
linux	sys: check that target consts are defined	2018-10-19 19:11:22 +01:00
netbsd	sys: check that target consts are defined	2018-10-19 19:11:22 +01:00
openbsd	sys: check that target consts are defined	2018-10-19 19:11:22 +01:00
syz-extract	sys: check that target consts are defined	2018-10-19 19:11:22 +01:00
syz-sysgen	Makefile: don't compile all targets into target binaries	2018-08-02 19:07:22 +02:00
targets	sys: check that target consts are defined	2018-10-19 19:11:22 +01:00
test	sys/linux: add syz_execute_func	2018-08-30 21:45:04 -07:00
windows	sys: check that target consts are defined	2018-10-19 19:11:22 +01:00
sys.go	Add mandatory OpenBSD bits (#689)	2018-08-28 10:07:26 -07:00