* 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.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 8c60e85e86367b4d0bcf56f0c189526bcc5d04c3..8bff539cd0de988df0503e26500e08103037a3ee 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,9 @@
+2009-05-14  Joel Brobecker  <brobecker@adacore.com>
+
+       * 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  <muller.u-strasbg.fr>
 
        Remove all i386 debug register low level macros in config nm files.

diff --git a/gdb/gdbarch.sh b/gdb/gdbarch.sh
index ee0efa8bf97dcdad3cc4dc6d5d33944d66641237..7e0d657dc7de8c177ad9ffb5a60fd0e3703e60c7 100755 (executable)
--- 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