From 9e2ace22e39209df7db5bd386107bab3cae32cb4 Mon Sep 17 00:00:00 2001 From: Joel Brobecker Date: Thu, 14 May 2009 19:16:28 +0000 Subject: [PATCH] * gdbarch.sh: Add comment documenting the target_gdbarch global. gdbarch.h does NOT need to be regenerated as the corresponding change has already been made in a previous commit. --- gdb/ChangeLog | 6 ++++++ gdb/gdbarch.sh | 11 +++++++++++ 2 files changed, 17 insertions(+) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 8c60e85e863..8bff539cd0d 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,9 @@ +2009-05-14 Joel Brobecker + + * gdbarch.sh: Add comment documenting the target_gdbarch global. + gdbarch.h does NOT need to be regenerated as the corresponding + change has already been made in a previous commit. + 2009-05-14 Pierre Muller Remove all i386 debug register low level macros in config nm files. diff --git a/gdb/gdbarch.sh b/gdb/gdbarch.sh index ee0efa8bf97..7e0d657dc7d 100755 --- a/gdb/gdbarch.sh +++ b/gdb/gdbarch.sh @@ -850,6 +850,17 @@ struct displaced_step_closure; struct core_regset_section; extern struct gdbarch *current_gdbarch; + +/* The architecture associated with the connection to the target. + + The architecture vector provides some information that is really + a property of the target: The layout of certain packets, for instance; + or the solib_ops vector. Etc. To differentiate architecture accesses + to per-target properties from per-thread/per-frame/per-objfile properties, + accesses to per-target properties should be made through target_gdbarch. + + Eventually, when support for multiple targets is implemented in + GDB, this global should be made target-specific. */ extern struct gdbarch *target_gdbarch; EOF -- 2.30.2