* gdbarch.h (target_gdbarch): Add comment documenting this global.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 8271e5a..3950030 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,10 +1,14 @@
-2009-05-06  Joel Brobecker   <brobecker@adacore.com>
+2009-05-07  Joel Brobecker  <brobecker@adacore.com>
+
+       * gdbarch.h (target_gdbarch): Add comment documenting this global.
+
+2009-05-06  Joel Brobecker  <brobecker@adacore.com>
 
        * acinclude.m4 (AM_ICONV): Prefer in-tree libiconv if present over
        system iconv.
        * configure: Regenerate.
 
-2009-05-06  Joel Brobecker   <brobecker@adacore.com>
+2009-05-06  Joel Brobecker  <brobecker@adacore.com>
 
        * utils.c: Add include of gdb_usleep.h.
        (defaulted_query): Detect false EOF conditions that happen

diff --git a/gdb/gdbarch.h b/gdb/gdbarch.h
index 5e508d7..e844f52 100644 (file)
--- a/gdb/gdbarch.h
+++ b/gdb/gdbarch.h
@@ -54,6 +54,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;