Discussion:
Valgrind: r16373 - in /trunk: NEWS docs/internals/3_12_BUGSTATUS.txt
Add Reply
s***@valgrind.org
2017-05-14 14:32:16 UTC
Reply
Permalink
Raw Message
Author: sewardj
Date: Sun May 14 15:32:15 2017
New Revision: 16373

Log:
Update.

Modified:
trunk/NEWS
trunk/docs/internals/3_12_BUGSTATUS.txt

Modified: trunk/NEWS
==============================================================================
--- trunk/NEWS (original)
+++ trunk/NEWS Sun May 14 15:32:15 2017
@@ -111,12 +111,15 @@
barrier implementation
358697 valgrind.h: Some code remains even when defining NVALGRIND
359202 Add musl libc configure/compile
+360415 amd64 instructions ADCX and ADOX are not implemented in VEX
+ == 372828 (vex amd64->IR: 0x66 0xF 0x3A 0x62 0x4A 0x10)
360429 unhandled ioctl 0x530d with no size/direction hints (CDROMREADMODE1)
362223 assertion failed when .valgrindrc is a directory instead of a file
367543 bt/btc/btr/bts x86/x86_64 instructions are poorly-handled wrt flags
367942 Segfault vgPlain_do_sys_sigaction (m_signals.c:1138)
368863 WARNING: unhandled arm64-linux syscall: 100 (get_robust_list)
368865 WARNING: unhandled arm64-linux syscall: 272 (kcmp)
+368868 disInstr(arm64): unhandled instruction 0xD53BE000 = cntfrq_el0 (ARMv8)
368917 WARNING: unhandled arm64-linux syscall: 218 (request_key)
368918 WARNING: unhandled arm64-linux syscall: 127 (sched_rr_get_interval)
368922 WARNING: unhandled arm64-linux syscall: 161 (sethostname)
@@ -130,6 +133,7 @@
371412 Rename wrap_sys_shmat to sys_shmat like other wrappers
371471 Valgrind complains about non legit memory leaks on placement new (C++)
371491 handleAddrOverrides() is [incorrect] when ASO prefix is used
+371503 disInstr(arm64): unhandled instruction 0xF89F0000
371869 support '%' in symbol Z-encoding
371916 execution tree xtree concept
372120 c++ demangler demangles symbols which are not c++

Modified: trunk/docs/internals/3_12_BUGSTATUS.txt
==============================================================================
--- trunk/docs/internals/3_12_BUGSTATUS.txt (original)
+++ trunk/docs/internals/3_12_BUGSTATUS.txt Sun May 14 15:32:15 2017
@@ -9,10 +9,6 @@
356715 vex amd64->IR: 0xC4 0xE2 0x7D 0x13 0x4 0x4A 0xC5 0xFC
vcvtph2ps (%rdx,%rcx,2),%ymm0

-(carried over)
-360415 amd64 instructions ADCX and ADOX are not implemented in VEX
- [has patch, could possibly take it, but needs cleanup/verification]
-
369409 vex amd64->IR: 0x48 0xF 0xC7 0xF0 0x72 0x2 0xE2 0xF8 (

372828 vex amd64->IR: 0x66 0x4D 0xF 0x38 0xF6 0xD2 0x66 0x4D
@@ -55,9 +51,6 @@

373990 Potential shift left overflow in guest_arm_toIR.c

-368868 disInstr(arm64): unhandled instruction 0xD53BE000 = cntfrq_el0 (ARMv8)
- (should fix this for 3.13?)
-
369459 valgrind on arm64 violates the ARMv8 spec (ldxr/stxr)
[fixed with --sim-hints=fallback-llsc?]

@@ -73,15 +66,10 @@

=== VEX/arm64 ==========================================================

-368868 disInstr(arm64): unhandled instruction 0xD53BE000 = cntfrq_el0 (ARMv8)
- (should fix this for 3.12.1)
-
369459 valgrind on arm64 violates the ARMv8 spec (ldxr/stxr)

369509 ARMv8.1 LSE instructions are not supported

-371503 disInstr(arm64): unhandled instruction 0xF89F0000 (prfum)
-
377966 disInstr(arm64): unhandled instruction 0xD50B7425

=== VEX/x86 ============================================================
@@ -497,21 +485,12 @@
352364 ppc64: --expensive-definedness-checks=yes is not quite working here

**
-360415 amd64 instructions ADCX and ADOX are not implemented in VEX
- [has a plausible patch]
- == 372828 (vex amd64->IR: 0x66 0xF 0x3A 0x62 0x4A 0x10)
-
-**
(carried over)
368507 valgrind throws std::bad_alloc on memory allocations larger
than 34255421416 bytes
(increase usable address space post release, on trunk)

**
-368868 disInstr(arm64): unhandled instruction 0xD53BE000 = cntfrq_el0 (ARMv8)
- (should fix this for 3.12.1)
-
-**
369459 valgrind on arm64 violates the ARMv8 spec (ldxr/stxr)
(is mostly fixed)

@@ -520,11 +499,6 @@
(easy patch)

**
-371503 disInstr(arm64): unhandled instruction 0xF89F0000
-
-**
-
-**
374963 increase valgrind's load address to prevent mmap failure
maybe change to 0x5800'0000

Loading...