deesix ae897dcfdb tests: no --exec_enable in hex2 calls because it's "Effectively a NOP" ... hex2 in mescc-tools defaults to executable output file since 1.0.0. See 0a553f720d39dae4231611671e4163a2d2422e0a there. This completes the removal started in Knight scripts during their M2libc migration at f2094a9e5b Note that test0101 compiles "hex2 0.3" and verifies that it works by linking an example. Calls to test/results/test0101-*-binary never used the flag because we don't call the linked example (we just check its SHA-256).		2021-01-23 00:00:00 +01:00
..
break-for.c	Catch potential segfaulting behavior in generated binaries	2020-11-08 21:13:12 -05:00
hello-aarch64.sh	tests: no --exec_enable in hex2 calls because it's "Effectively a NOP"	2021-01-23 00:00:00 +01:00
hello-amd64.sh	tests: no --exec_enable in hex2 calls because it's "Effectively a NOP"	2021-01-23 00:00:00 +01:00
hello-armv7l.sh	tests: no --exec_enable in hex2 calls because it's "Effectively a NOP"	2021-01-23 00:00:00 +01:00
hello-knight-native.sh	tests: no --exec_enable in hex2 calls because it's "Effectively a NOP"	2021-01-23 00:00:00 +01:00
hello-knight-posix.sh	Migrate knight-posix to M2libc	2021-01-22 00:35:43 -05:00
hello-x86.sh	tests: no --exec_enable in hex2 calls because it's "Effectively a NOP"	2021-01-23 00:00:00 +01:00
proof.answer	Major relocation of tests to better structure for future additions	2020-02-28 18:27:12 -05:00