Some test scripts run programs that return non-zero values for correct
outcome; those would fail the shell -e checks.
But some scripts not using -e are fine with it because we expect zero or
the error condition is handled otherwise. So, for robustness, the option is
added into them.
This completes the transition started in Knight scripts during their M2libc
migration at f2094a9e5b
from : to
--BaseAddress : --base-address
--BigEndian : --big-endian
--LittleEndian : --little-endian
The plan for mescc-tools is to deprecate the old (pre-1.0.0) flags.
Note that test0101 compiles "hex2 0.3" and verifies that it works by
linking an example. This 0.3 version requires the old-style flags, so the
calls to test/results/test0101-*-binary are left unchanged.
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).
We were checking an empty proof because the test writes to stderr and we
were redirecting stdout to the file. With the correct redirection the hash
is different, so proof.answer is also adjusted.
The x86 test was calling blood-elf with the 64bits flag. Removed to ask for
32bits behaviour.
For consistency, --BaseAddress is now using the usual value for the arch.
Also, unused input file is removed here.
Every AArch64 test script is affected because AArch64 -> aarch64. test0101
needs i386 -> x86 because it verifies the resulting AArch64 binary (hex2)
creating some x86 proof.
Also, a couple of x86 tests (test0000 and test0025) that are M2libc aware,
again because i386 -> x86 (hex2 ELF parts).