mirror of
https://github.com/cc65/cc65.git
synced 2024-12-22 12:30:41 +00:00
d7a804d120
Some tests pipe the stdout and stderr of the compiler or assembler into a file and compare the result with a reference. This has the subtle problem that both stdout and stderr and buffered i/o streams that may or may not work the same on different OSs or even shells. That means the order of the lines in the resulting file is not guaranteed. In practise it is "mostly" not an issue, but "we" still stumbled about one test where different behaviour can be triggered depending on running it in cmd.exe or bash (msys): test/asm/listing output of 010-paramcount.bin differs from the reference output when running the test from cmd.exe. The solution is most likely to have two reference files and not redirect into one file. This patch fixes the issue (cf. #1912) for the directory test/asm/. |
||
|---|---|---|
| .. | ||
| cpudetect | ||
| err | ||
| listing | ||
| opcodes | ||
| val | ||
| Makefile | ||
| readme.txt | ||
Assembler Testcases =================== Opcode Tests: ------------- these go into opcodes/. Refer to opcodes/readme.txt CPU Detect Tests ---------------- these go into cpudetect/. Refer to cpudetect/readme.txt Overall tests: -------------- These go into listing/. Refer to listing/readme.txt val: ---- Works very much like the /val directory used to test the compiler - individual tests are run in the simulator and should exit with an exit code of 0 when they pass, or either -1 or a number indicating what part of the test failed on error. err: ---- Works very much like the /err directory used to test the compiler - individual tests are assembled and MUST NOT assemble without error.