Re: [Valgrind-developers] size of the various tools and nr of supported architectures ....

[Philippe W. <phi...@sk...>]

On Mon, 2015-03-30 at 23:13 +0200, Philippe Waroquiers wrote:
> An advantage of option 2.5 is that main_main.c will always be compiled
> in both VEXMULTIARCH and single arch mode, to help catching an unlikely
> compilation bug in VEXMULTIARCH not detected otherwise.
> 
> A user that needs multi arch can then have it just
> by giving 2 libs to link (in the good order) :
>    libvexmultiarch-x86-linux.a libvex-x86-linux.a
> where the first lib only contains main_main.c compiled with VEXMULTIARCH
> defined. The 2nd lib contains main_main.c compiled in single arch,
> and all the other VEX object files, and is the one to use by default.
> 

Option '2.5' committed as vex: r3113 

So, the VEX user can choose at link time whether single arch or
multi-arch VEX is linked in.

Example:
  # this produces t1single (calling LibVEX_Translate), that is single arch:
  gcc -o t1single t1.o -LInst/lib/valgrind  -lvex-x86-linux -lgcc

  # this produces t1multi, that is multi arch:
  gcc -o t1multi t1.o -LInst/lib/valgrind  -lvexmultiarch-x86-linux -lvex-x86-linux -lgcc

Philippe