aboutsummaryrefslogtreecommitdiff
path: root/gdb/dwarf2/expr.h
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@efficios.com>2022-12-13 22:34:33 -0500
committerSimon Marchi <simon.marchi@efficios.com>2023-01-20 14:48:57 -0500
commit1298c32f01b3ae90fb17665f9b9b01c932767fd5 (patch)
treef147eb6f022b0246e679858f89215a30976e5f17 /gdb/dwarf2/expr.h
parentb23bf9f7241caecc41127a5739dfb32788b041a6 (diff)
downloadgdb-1298c32f01b3ae90fb17665f9b9b01c932767fd5.zip
gdb-1298c32f01b3ae90fb17665f9b9b01c932767fd5.tar.gz
gdb-1298c32f01b3ae90fb17665f9b9b01c932767fd5.tar.bz2
gdb: move call site types to call-site.h
I hesitated between putting the file in the dwarf2 directory (as gdb/dwarf2/call-site.h) or in the common directory (as gdb/call-site.h). The concept of call site is not DWARF-specific, another debug info reader could provide this information. But as it is, the implementation is a bit DWARF-specific, as one form it can take is a DWARF expression and parameters can be defined using a DWARF register number. So I ended up choosing to put it under dwarf2/. If another debug info reader ever wants to provide call site information, we can introduce a layer of abstraction between the "common" call site and the "dwarf2" call site. The copyright start year comes from the date `struct call_site` was introduced. Change-Id: I1cd84aa581fbbf729edc91b20f7d7a6e0377014d Reviewed-By: Bruno Larsen <blarsen@redhat.com>
Diffstat (limited to 'gdb/dwarf2/expr.h')
-rw-r--r--gdb/dwarf2/expr.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/dwarf2/expr.h b/gdb/dwarf2/expr.h
index 4d93a96..44fc645 100644
--- a/gdb/dwarf2/expr.h
+++ b/gdb/dwarf2/expr.h
@@ -23,7 +23,7 @@
#define DWARF2EXPR_H
#include "leb128.h"
-#include "gdbtypes.h"
+#include "dwarf2/call-site.h"
struct dwarf2_per_objfile;