aboutsummaryrefslogtreecommitdiff
path: root/gdb/arch-utils.h
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@polymtl.ca>2021-06-28 11:49:22 -0400
committerSimon Marchi <simon.marchi@polymtl.ca>2021-06-28 11:49:22 -0400
commitb447dd03c16d51c7b41c9af0756fc9db4ad95f0d (patch)
tree4cff1537b99c800351a42d293650b7c51459e710 /gdb/arch-utils.h
parentc87c999c511f0484de53fa616b0bf6b00c753434 (diff)
downloadgdb-b447dd03c16d51c7b41c9af0756fc9db4ad95f0d.zip
gdb-b447dd03c16d51c7b41c9af0756fc9db4ad95f0d.tar.gz
gdb-b447dd03c16d51c7b41c9af0756fc9db4ad95f0d.tar.bz2
gdb: remove gdbarch_info_init
While reviewing another patch, I realized that gdbarch_info_init could easily be removed in favor of initializing gdbarch_info fields directly in the struct declaration. The only odd part is the union. I don't know if it's actually important for it to be zero-initialized, but I presume it is. I added a constructor to gdbarch_info to take care of that. A proper solution would be to use std::variant. Or, these could also be separate fields, the little extra space required wouldn't matter. gdb/ChangeLog: * gdbarch.sh (struct gdbarch_info): Initialize fields, add constructor. * gdbarch.h: Re-generate. * arch-utils.h (gdbarch_info_init): Remove, delete all usages. * arch-utils.c (gdbarch_info_init): Remove. Change-Id: I7502e08fe0f278d84eef1667a072e8a97bda5ab5
Diffstat (limited to 'gdb/arch-utils.h')
-rw-r--r--gdb/arch-utils.h6
1 files changed, 0 insertions, 6 deletions
diff --git a/gdb/arch-utils.h b/gdb/arch-utils.h
index a5b40ad..03e9082 100644
--- a/gdb/arch-utils.h
+++ b/gdb/arch-utils.h
@@ -196,12 +196,6 @@ extern enum bfd_endian selected_byte_order (void);
was explicitly selected. */
extern const char *selected_architecture_name (void);
-/* Initialize a ``struct info''. Can't use memset(0) since some
- default values are not zero. "fill" takes all available
- information and fills in any unspecified fields. */
-
-extern void gdbarch_info_init (struct gdbarch_info *info);
-
/* Similar to init, but this time fill in the blanks. Information is
obtained from the global "set ..." options and explicitly
initialized INFO fields. */