aboutsummaryrefslogtreecommitdiff
path: root/gdb/gdbsupport
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2019-09-19 13:17:59 -0400
committerAndrew Burgess <andrew.burgess@embecosm.com>2019-10-02 14:05:50 +0100
commit554ac434b02465f1fc925b0ae3393fb841e0d59c (patch)
tree0e897b27e89aee707954da34cedf0a95881f8e7f /gdb/gdbsupport
parent46f29a9a260da1a03176682aff63bad03d8f2e8b (diff)
downloadgdb-554ac434b02465f1fc925b0ae3393fb841e0d59c.zip
gdb-554ac434b02465f1fc925b0ae3393fb841e0d59c.tar.gz
gdb-554ac434b02465f1fc925b0ae3393fb841e0d59c.tar.bz2
gdb: Change a VEC to std::vector in btrace.{c,h}
Replace a VEC with a std::vector in btrace.h, and update btrace.c to match. It is worth noting that this code appears to be currently untested by the GDB testsuite. I've tried to do a like for like replacement when moving to std::vector, with minimal refactoring to try and avoid introducing any bugs. As the new vector is inside a union I've currently used a pointer to vector, which makes the code slightly uglier than it might otherwise be, but again, due to lack of testing I'm reluctant to start refactoring the code in a big way. gdb/ChangeLog: * btrace.c (btrace_maint_clear): Update to handle change from VEC to std::vector. (btrace_maint_decode_pt): Likewise, and move allocation of the vector outside of the loop. (btrace_maint_update_packets): Update to handle change from VEC to std::vector. (btrace_maint_print_packets): Likewise. (maint_info_btrace_cmd): Likewise. * btrace.h: Remove use of DEF_VEC_O. (typedef btrace_pt_packet_s): Delete. (struct btrace_maint_info) <packets>: Change fromm VEC to std::vector. * gdbsupport/btrace-common.h: Remove 'vec.h' include.
Diffstat (limited to 'gdb/gdbsupport')
-rw-r--r--gdb/gdbsupport/btrace-common.h2
1 files changed, 0 insertions, 2 deletions
diff --git a/gdb/gdbsupport/btrace-common.h b/gdb/gdbsupport/btrace-common.h
index 9c57645..166d7b1 100644
--- a/gdb/gdbsupport/btrace-common.h
+++ b/gdb/gdbsupport/btrace-common.h
@@ -26,8 +26,6 @@
inferior. For presentation purposes, the branch trace is represented as a
list of sequential control-flow blocks, one such list per thread. */
-#include "vec.h"
-
/* A branch trace block.
This represents a block of sequential control-flow. Adjacent blocks will be