aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKimplul <kimi.h.kuparinen@gmail.com>2023-08-26 21:10:34 +0300
committerGitHub <noreply@github.com>2023-08-26 21:10:34 +0300
commit4d8fdd4288cc3ca5e0a2bd6ac80b725c2ee52118 (patch)
tree0f698787460689795d01ac99c34dc69caf4f1f10
parent4269b6d3d0aeff1cf1bae3eac5f40cceb75576e0 (diff)
downloadcopyjit-4d8fdd4288cc3ca5e0a2bd6ac80b725c2ee52118.tar.gz
copyjit-4d8fdd4288cc3ca5e0a2bd6ac80b725c2ee52118.zip
Update README.md
-rw-r--r--README.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/README.md b/README.md
index a1a4620..a3d4a29 100644
--- a/README.md
+++ b/README.md
@@ -141,14 +141,14 @@ with the same architecture string as the GCC tests.
For instance, a GCC test case:
```
-make CROSS_COMPILE=riscv64-linux-gnu- ARCH=riscv64 -j$(nproc)
-qemu-riscv64 -L /usr/riscv64-linux-gnu ./copyjit
+make CROSS_COMPILE=riscv64-linux-gnu- ARCH=riscv64 -j$(nproc) examples
+qemu-riscv64 -L /usr/riscv64-linux-gnu ./examples/copyjit
```
And an LLVM test case:
```
-make CROSS_COMPILE=riscv64-linux-gnu- ARCH=riscv64 -j$(nproc)
-qemu-riscv64 -L /usr/riscv64-linux-gnu ./copyjit
+make CROSS_COMPILE=riscv64-linux-gnu- ARCH=riscv64 -j$(nproc) examples
+qemu-riscv64 -L /usr/riscv64-linux-gnu ./examples/copyjit
```
Some of the 'broken' architectures may end up working with some compiler flag
@@ -171,7 +171,7 @@ OK:
+ `arm`
Broken:
-+ `mips64el` (possibly due to bug in instruction cache flushing? otherwise unsure)
++ `mips64el` (issues with ABI, global pointer?)
+ `mips64`
+ `mipsel`
+ `mips`