secondary BSD tier `build test` status after llvm 13 bump

[mikdusan]

note: purpose of this issue is to record status/patches/workarounds (issue will be closed immediately)

status	os	arch	command	llvm13-patches	note
✅	netbsd 9.2	amd64	sudo -E zig build test	netbsd.zip	note 1
✅	openbsd 7.0	amd64	MALLOC_OPTIONS=CFGJ zig build test	openbsd.zip	note 2,3,4
✅	dragonfly 6.0	x86_64	zig build test

note 1 (netbsd) workaround file lock limit

• must run as root to overcome per-user file lock limits

---

note 2 (openbsd) open file limit

• triggered by zig build-exe hello.zig -target native-linux -lc
• edit /etc/login.conf
• bump per-user open file limit in default class to:

    :openfiles-max=2048:\
    :openfiles-cur=2048:\

• logout/login to effect changes

---

note 3 (openbsd) increase file lock limit

• triggered by zig build-exe hello.zig -target native-linux -lc

sysctl kern.maxlocksperuid=2048

---

note 4 (openbsd) workaround use-after-free

• use-after-free is triggered by test 'undefined as field type is rejected' failed: CompilationCrashed
• workaround by just fiddling with malloc options to not do whatever default openbsd behavior is

[semarie]

@mikdusan I just saw your issue now.

The note 4 trigger me a bit 😃. if a use-after-free is found by libc on OpenBSD, it means or libc on OpenBSD is wrong (and it should be corrected) or zig did bad thing (and it should be corrected). but using malloc_options to avoid triggering it isn't the right way, specially if it affects all tests.

if the test do volontary a use-after-free, the test should be disabled for OpenBSD.

[mikdusan]

if the test do volontary a use-after-free, the test should be disabled for OpenBSD.

I'm pretty sure zig stage1 (c++) sources are responsible for the uaf and agree that test should be disabled for OpenBSD.