|
From: <sv...@va...> - 2014-02-21 14:55:02
|
Author: sewardj
Date: Fri Feb 21 14:54:51 2014
New Revision: 13827
Log:
Update.
Modified:
trunk/README.aarch64
Modified: trunk/README.aarch64
==============================================================================
--- trunk/README.aarch64 (original)
+++ trunk/README.aarch64 Fri Feb 21 14:54:51 2014
@@ -7,15 +7,14 @@
instructions and can run almost anything generated by gcc-4.8.2 -O2.
The port is under active development.
-Current limitations, as of mid-Jan 2014.
+Current limitations, as of mid-Feb 2014.
-* threaded apps won't work, due to inadequate sys_clone() support.
-
-* almost no support of vector (SIMD) instructions
+* limited support of vector (SIMD) instructions. Initial target is
+ support for instructions created by gcc-4.8.2 -O3 (via vectorisation).
+ This is mostly complete.
* Integration with the built in GDB server:
- - basically works but breakpoints are causing crashes due to missing
- unchainXDirect_ARM64 needed by LibVEX_UnChain.
+ - basically works but breakpoints may be problematic (unclear)
Use --vgdb=full to bypass the problem.
- still to do:
arm64 xml register description files (allowing shadow registers
@@ -23,11 +22,18 @@
ptrace invoker : currently disabled for both arm and arm64
cpsr transfer to/from gdb to be looked at (see also arm equivalent code)
+* limited syscall support
+
There has been extensive testing of the baseline simulation of integer
and FP instructions. Memcheck is also believed to work, at least for
small examples. Other tools appear to at least not crash when running
/bin/date.
+Enough syscalls are supported for /bin/ssh and /bin/bash to work. In
+particular that means that programs that create and use TCP sockets
+are likely to work.
+
+
Building
~~~~~~~~
@@ -231,3 +237,6 @@
math_MINMAXV: use real Iop_Cat{Odd,Even}Lanes ops rather than
inline scalar code
+
+
+chainXDirect_ARM64: use direct jump forms when possible
|