Re: [Valgrind-developers] Followup to c5218ff4c and some VEX cleanup

[Paul F. <pj...@wa...>]

On 7/6/25 17:55, Florian Krohm wrote:
>
> Does that all sound OK ?
>
Hi Florian


For point 2

hd_fpu.c looks very old, pre-Valgrind even. The missing header looks 
like a precursor to config.h and will probably be fairly easy to 
recreate.  It looks like it's meant to create an object file that is a 
dependency for ...

x87_to_vex_and_back.c which is missing some riscv64 pieces. I'd need to 
get it working in order to comment how useful it might be. Our x87 
support is not great, but no-one has time to work on it.

smchash.c looks like a tool for checking hash values. Is that still of 
any use? Conceivably on new platforms.

For point 5, the initial commit comment is

     A very simple dynamic translator built on Vex, for the purpose of
     debugging Vex using the binary-search-switchback technique

The Makefile refers to the ppc static library, so needs modifying to 
work on any other platform.


Maybe all these files should be in an "attic" directly with some text 
saying that they are mostly forgotten.


Back in "useful",

Is Makefile-vex any use? It needs work on my system and it just builds 
libvex.a. Is that any different to the autotools produced 
VEX/libvex-ARCH-OS.a? It just looks a bit smaller.

Regards

Paul