|
From: Dave N. <dc...@us...> - 2005-11-15 22:29:20
|
On Tue, 14 Nov 2005, Nicholas Nethercote wrote: +- AMD64 support is much improved. The 64-bit vs. 32-bit issues in 3.0.0 + and 3.0.1 have been resolved, and it should "just work" now in all + cases. On AMD64 machines both 64-bit and 32-bit versions of Valgrind + are built. The right version will be invoked automatically, even when + using --trace-children and mixing execution between 64-bit and 32-bit + executables. Also, many more instructions are supported. I'm planning on porting Valgrind to ppc64. The consensus I am hearing from my group at IBM is that we would like a single 64-bit ppc program that can handle either 32-bit or 64-bit client programs. If I am understanding the above mail correctly, the AMD64 port opted to produce two separate Valgrind programs: 64-bit and 32-bit where the 32-bit program handles 32-bit clients and the 64-bit program handles 64-bit clients. Can anyone explain the rationale behind the two separate Valgrind programs vs. a single 64-bit Valgrind? Is this simply a performance issue or is there some aspect of the Valgrind architecture that would make it too difficult/impossible to create a single 64-bit Valgrind that handles both architectures? Would this limitation apply as well to ppc32/ppc64? |