Adding the start of the instruction test infrastructure.

This commit is contained in:
Ben Vanik 2013-01-27 02:51:53 -08:00
parent e37821cf36
commit 26d5df0d38
11 changed files with 402 additions and 0 deletions

37
test/codegen/Makefile Normal file
View file

@ -0,0 +1,37 @@
BINUTILS=../../build/binutils/
PPC_AS=$(BINUTILS)/gas/as-new
PPC_LD=$(BINUTILS)/ld/ld-new
PPC_OBJDUMP=$(BINUTILS)/binutils/objdump
SRCS=$(wildcard *.s)
BINS=$(SRCS:.s=.bin)
DISASMS=$(SRCS:.s=.dis)
%.o: %.s
$(PPC_AS) \
-a64 \
-be \
-mregnames \
-mpower7 \
-maltivec \
-mvsx \
-R \
-o $@ \
$<
%.dis: %.o
$(PPC_OBJDUMP) --adjust-vma=0x82010000 -Mpower7 -D -EB $< > $@
%.bin: %.o
$(PPC_LD) \
-A powerpc:common64 \
-melf64ppc \
-EB \
-nostdlib \
--oformat binary \
-Ttext 0x82010000 \
-e 0x82010000 \
-o $@ \
$<
all: $(BINS) $(DISASMS)

61
test/codegen/README.md Normal file
View file

@ -0,0 +1,61 @@
# Codegen Tests
This directory contains the test assets used by the automated codegen test
runner.
Each test is structured as a source `[name].s` PPC assembly file and the
generated outputs. The outputs are made using the custom build of binutils
setup when `xenia-build setup` is called and are checked in to make it easier
to run the tests on Windows.
Tests are run using the `xenia-test` app or via `xenia-build test`.
## Execution
The test binary is placed into memory at `0x82010000` and all other memory is
zeroed.
All registers are reset to zero. In order to provide useful inputs tests can
specify `# REGISTER_IN` values.
The code is jumped into at the starting address and executed until the last
instruction in the input file is reached.
After all instructions complete any `# REGISTER_OUT` values are checked and if
they do not match the test is failed.
## Annotations
Annotations can appear at any line in a file. If a number is required it can
be in either hex or decimal form, or IEEE if floating-point.
### REGISTER_IN
```
# REGISTER_IN [register name] [register value]
```
Sets the value of a register prior to executing the instructions.
Examples:
```
# REGISTER_IN r4 0x1234
# REGISTER_IN r4 5678
```
### REGISTER_OUT
```
# REGISTER_OUT [register name] [register value]
```
Defines the expected register value when the instructions have executed.
If after all instructions have completed the register value does not match
the value given here the test will fail.
Examples:
```
# REGISTER_OUT r3 123
```
TODO: memory setup/assertions

1
test/codegen/ori.bin Executable file
View file

@ -0,0 +1 @@
`<60><><EFBFBD>

8
test/codegen/ori.dis Normal file
View file

@ -0,0 +1,8 @@
ori.o: file format elf64-powerpc
Disassembly of section .text:
0000000082010000 <.text>:
82010000: 60 83 ff ff ori r3,r4,65535

5
test/codegen/ori.s Normal file
View file

@ -0,0 +1,5 @@
# REGISTER_IN r4 0xDEADBEEFCAFEBABE
ori r3, r4, 0xFFFF
# REGISTER_OUT r3 0xBABE