Lines Matching refs:AMD64

7 This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux,
8 PPC64/Linux, S390X/Linux, ARM/Android, X86/Darwin and AMD64/Darwin.
366 This release supports X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux,
367 PPC64/Linux, X86/Darwin and AMD64/Darwin.  Support for recent distros
686 This release supports X86/Linux, AMD64/Linux, PPC32/Linux, PPC64/Linux
729   - 32-bit programs on x86 and AMD64 (a.k.a x86-64) machines are supported
733   - 64-bit programs on x86 and AMD64 (a.k.a x86-64) machines are not
1291 AMD64/Linux, PPC32/Linux and PPC64/Linux.  Support for recent distros
1533 AMD64/Linux, PPC32/Linux and PPC64/Linux.  Support for recent distros
1941 AMD64/Linux, PPC32/Linux and PPC64/Linux.
1968   AMD64/Linux.
1982 - Valgrind now works on PPC64/Linux.  As with the AMD64/Linux port,
2176 AMD64 support is much improved, PPC32 support is good enough to be
2180 - AMD64 support is much improved.  The 64-bit vs. 32-bit issues in
2182   cases.  On AMD64 machines both 64-bit and 32-bit versions of
2288         binaries on AMD64
2320 112031  iopl on AMD64 and README_MISSING_SYSCALL_OR_IOCTL update
2370 110652  AMD64 valgrind crashes on cwtd instruction
2371 110653  AMD64 valgrind crashes on sarb $0x4,foo(%rip) instruction
2408 x86.  The new architectures it supports are AMD64 and PPC32, and the
2411 AMD64 support works well, but has some shortcomings:
2420 - If Valgrind is built on an AMD64 machine, it will only run 64-bit
2422   on an AMD64, you will need to build Valgrind on an x86 machine and
2423   copy it to the AMD64 machine.  And it probably won't work if you do
2438   Without PIE enabled, AMD64 programs will only be able to access 2GB of
2494 - As part of adding AMD64 support, DWARF2 CFI-based stack unwinding
2521 109429  AMD64 unhandled syscall: 127 (sigpending)
2526 109363  AMD64 unhandled instruction bytes 
2527 109362  AMD64 unhandled syscall: 24 (sched_yield)
2844 * Fix to allow 32-bit Valgrind to run on AMD64 boxes.  Note: this does
2846   executables on an AMD64 box.