aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/lib/gdb-python.exp
diff options
context:
space:
mode:
authorJan Beulich <jbeulich@suse.com>2022-06-13 09:53:23 +0200
committerJan Beulich <jbeulich@suse.com>2022-06-13 09:53:23 +0200
commit95ff67183492ef847b181346a83485b38d0906c4 (patch)
tree27ccab4922bc77e645533847a30f2ad485093327 /gdb/testsuite/lib/gdb-python.exp
parent32f06c69f2284bc925e8d56fecbfc2a3f9f7301f (diff)
downloadgdb-95ff67183492ef847b181346a83485b38d0906c4.zip
gdb-95ff67183492ef847b181346a83485b38d0906c4.tar.gz
gdb-95ff67183492ef847b181346a83485b38d0906c4.tar.bz2
x86: replace global scratch buffer
With its movement to the stack, and with the subsequent desire to initialize the entire instr_info instances, this has become doubly inefficient. Individual users have better knowledge of how big a buffer they need, and in a number of cases going through an intermediate buffer can be avoided altogether. Having got confirmation that it wasn't intentional to print memory operand displacements with inconsistent style, print_displacement() is now using dis_style_address_offset consistently (eliminating the need for callers to pass in a style). While touching print_operand_value() also convert its "hex" parameter to bool. And while altering (and moving) oappend_immediate(), fold oappend_maybe_intel_with_style() into its only remaining caller. Finally where doing adjustments, use snprintf() in favor of sprintf().
Diffstat (limited to 'gdb/testsuite/lib/gdb-python.exp')
0 files changed, 0 insertions, 0 deletions