Markus Metzger da8c46d296 btrace: indicate speculative execution ... Indicate speculatively executed instructions with a leading '?'. We use the space that is normally used for the PC prefix. In the case where the instruction at the current PC had been executed speculatively before, the PC prefix will be partially overwritten resulting in "?> ". As a side-effect, the /p modifier to omit the PC prefix in the "record instruction-history" command now uses a 3-space PC prefix " " in order to have enough space for the speculative execution indication. gdb/ * btrace.c (btrace_compute_ftrace_bts): Clear insn flags. (pt_btrace_insn_flags): New. (ftrace_add_pt): Call pt_btrace_insn_flags. * btrace.h (btrace_insn_flag): New. (btrace_insn) <flags>: New. * record-btrace.c (btrace_insn_history): Print insn prefix. * NEWS: Announce it. doc/ * gdb.texinfo (Process Record and Replay): Document prefixing of speculatively executed instructions in the "record instruction-history" command. testsuite/ * gdb.btrace/instruction_history.exp: Update. * gdb.btrace/tsx.exp: New. * gdb.btrace/tsx.c: New. * lib/gdb.exp (skip_tsx_tests, skip_btrace_pt_tests): New.		2015-08-07 10:22:39 +02:00
..
buffer-size.exp
data.c
data.exp
delta.exp
enable.c
enable.exp
exception.cc
exception.exp
function_call_history.c
function_call_history.exp
gcore.exp
i686-record_goto.S
i686-tailcall.S
instruction_history.c
instruction_history.exp
instruction_history.S
Makefile.in
multi-thread-step.c
multi-thread-step.exp
nohist.exp
record_goto-step.exp
record_goto.c
record_goto.exp
rn-dl-bind.c
rn-dl-bind.exp
segv.c
segv.exp
step.exp
stepi.exp
tailcall.c
tailcall.exp
tsx.c
tsx.exp
unknown_functions.c
unknown_functions.exp
vdso.c
vdso.exp
x86_64-record_goto.S
x86_64-tailcall.S
x86-tsx.S