linux/tools/testing/selftests/nolibc
Thomas Weißschuh a782d45c86 selftests/nolibc: stop testing constructor order
The execution order of constructors in undefined and depends on the
toolchain.  While recent toolchains seems to have a stable order, it
doesn't work for older ones and may also change at any time.

Stop validating the order and instead only validate that all
constructors are executed.

Reported-by: Willy Tarreau <w@1wt.eu>
Closes: https://lore.kernel.org/lkml/20250301110735.GA18621@1wt.eu/
Link: https://lore.kernel.org/r/20250306-nolibc-constructor-order-v1-1-68fd161cc5ec@weissschuh.net
Acked-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
2025-03-07 07:34:12 +01:00
..
.gitignore selftests/nolibc: add script to run testsuite 2023-12-11 22:38:17 +01:00
Makefile selftests/nolibc: add armthumb configuration 2025-03-02 13:25:20 +01:00
nolibc-test-linkage.c selftests/nolibc: stop testing constructor order 2025-03-07 07:34:12 +01:00
nolibc-test-linkage.h selftests/nolibc: add tests for multi-object linkage 2023-10-12 21:14:20 +02:00
nolibc-test.c selftests/nolibc: stop testing constructor order 2025-03-07 07:34:12 +01:00
run-tests.sh selftests/nolibc: add armthumb configuration 2025-03-02 13:25:20 +01:00