Rationalise --vex-guest* flags in the new IRSB construction framework
commit56e04256a7a317d15240677e5bd322c0a039f66b
authorJulian Seward <jseward@acm.org>
Mon, 18 Nov 2019 18:12:49 +0000 (18 19:12 +0100)
committerJulian Seward <jseward@acm.org>
Thu, 2 Jan 2020 05:42:21 +0000 (2 06:42 +0100)
tree921ca1ae206eb17721719ae2961ed7f333180287
parent0d8e6482be47f29a8527e9f8da16c3689f954c2f
Rationalise --vex-guest* flags in the new IRSB construction framework

* removes --vex-guest-chase-cond=no|yes.  This was never used in practice.

* rename --vex-guest-chase-thresh=<0..99> to --vex-guest-chase=no|yes.  In
  otherwords, downgrade it from a numeric flag to a boolean one, that can
  simply disable all chasing if required.  (Some tools, notably Callgrind,
  force-disable block chasing, so this functionality at least needs to be
  retained).
VEX/priv/guest_generic_bb_to_IR.c
VEX/pub/libvex.h
callgrind/main.c
coregrind/m_main.c
docs/xml/manual-core-adv.xml
exp-bbv/bbv_main.c
exp-sgcheck/pc_main.c
helgrind/hg_main.c
none/tests/cmdline2.stdout.exp