Put bcache inside "namespace gdb"
This avoids a conflict with a system "struct bcache" on Solaris (see e.g. https://www.isi.edu/nsnam/archive/ns-users/webarch/2001/msg05393.html) Note that the Solaris conflict for now only surfaces with --enable-targets=all (which the build bot doesn't use). gdb/ChangeLog: 2019-12-06 Christian Biesinger <cbiesinger@google.com> * bcache.c: Put in namespace gdb. * bcache.h: Likewise. * gdbtypes.c (check_types_worklist): Update. (types_deeply_equal): Update. * macrotab.c (struct macro_table) <bcache>: Update. (new_macro_table): Update. * macrotab.h (struct bcache): Put this forward declaration inside namespace gdb. (new_macro_table): Update. * objfiles.h (struct objfile_per_bfd_storage) <filename_cache>: Update. <macro_cache>: Update. * psymtab.h: (psymtab_storage) <psymbol_cache>: Update. Change-Id: I843d5e91f7ccb3db6d1099a8214c15a74510256f
This commit is contained in:
parent
93e55f0a03
commit
dfb65191d8
8 changed files with 36 additions and 9 deletions
|
@ -23,9 +23,12 @@
|
|||
#include "gdbsupport/function-view.h"
|
||||
|
||||
struct obstack;
|
||||
struct bcache;
|
||||
struct compunit_symtab;
|
||||
|
||||
namespace gdb {
|
||||
struct bcache;
|
||||
}
|
||||
|
||||
/* How do we represent a source location? I mean, how should we
|
||||
represent them within GDB; the user wants to use all sorts of
|
||||
ambiguous abbreviations, like "break 32" and "break foo.c:32"
|
||||
|
@ -170,7 +173,7 @@ struct macro_source_file
|
|||
the same source location (although 'gcc -DFOO -UFOO -DFOO=2' does
|
||||
do that in GCC 4.1.2.). */
|
||||
struct macro_table *new_macro_table (struct obstack *obstack,
|
||||
struct bcache *bcache,
|
||||
gdb::bcache *bcache,
|
||||
struct compunit_symtab *cust);
|
||||
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue