kmi/tests/scripts/makefile, branch masterACTIVE - Kernel with migrating threads as IPChttps://metanimi.dy.fi/cgit/kmi/atom?h=master2026-01-25T15:14:53Zimplement dmem semi-properly2026-01-25T15:14:53ZKimplulkimi.h.kuparinen@gmail.com2026-01-25T15:14:53Zurn:sha1:cd41ed1758f4842d7b78870385e16b579cc89c38
+ Add tests and fix virtual mapping, this is enough to start writing
proper userspace drivers
allow reading fdt in tests2026-01-25T13:07:04ZKimplulkimi.h.kuparinen@gmail.com2026-01-25T13:07:04Zurn:sha1:e8a7fe3bd5c40168d531a6a4f00a7417a278d58csimplify generator scripts2025-04-22T18:09:09ZKimplulkimi.h.kuparinen@gmail.com2025-04-22T18:09:09Zurn:sha1:9d735045e0b73b46443f9dacd1b42f5ac3e734deinitial exec support2024-11-02T13:28:23ZKimplulkimi.h.kuparinen@gmail.com2024-11-02T13:28:23Zurn:sha1:d127146846f4d6561e15000d1469b715dafdb627specify mabi and march2024-08-30T15:52:55ZKimplulkimi.h.kuparinen@gmail.com2024-08-30T15:52:55Zurn:sha1:5cc76c436fa1234323bad51d72d1291d95991da6simplify tests2024-08-26T15:34:24ZKimplulkimi.h.kuparinen@gmail.com2024-08-26T15:34:24Zurn:sha1:eff7f52c368df5dc662d54956de5aa3b2b9ee936add malloc test2024-08-21T20:31:48ZKimplulkimi.h.kuparinen@gmail.com2024-08-21T20:31:48Zurn:sha1:97ffab0a8472981b927d0f4e81bb72f6ecd69b86small fixes to issues reported by analyzer2024-08-17T21:17:35ZKimplulkimi.h.kuparinen@gmail.com2024-08-17T21:17:35Zurn:sha1:ab011165cd440b5535d39febd8118e3e26b64b57
+ Currently analyzer has to be run manually with something like
make CFLAGS='-fanalyzer -Wno-analyzer-infinite-loop'
I use an infinite loop as an assert, I know it's not great/technically
UB but it's just a fallback.
+ Analyzer is still somewhat limited, I could add in more
attributes about different functions, such as memory allocation sizes
etc.
+ If I ever set up a CI pipeline, remember to use analyzer?
make tests a bit more sensible2024-07-17T19:02:47ZKimplulkimi.h.kuparinen@gmail.com2024-07-17T19:02:47Zurn:sha1:1a0d61b33c2365cf413bf584289058d0d9097377
+ At least by my standards. Some amount of scripting going on, but
should still be fine.
Effectively, source.mk contains information to build the test,
check.mk checks the generated log from running the test. As a results,
check.mk should output OK into reports/$TEST/OK if everything went
well, and anything else otherwise. The user can then look at
reports/$TEST/log to see what went wrong.
I expect to add some more features, such as starting QEMU with gdb and
running a single test a bit easier than right now (same limitation as
in the top level makefile, i.e. you have to specify
make -f scripts/makefile $TEST
from within `tests` and you must have ran `make check` at that point
so that `tests.mk` is fully generated. Not huge issues, but slightly
annoying, somewhat unsure how to work around them properly but we'll
see.