* gdbarch.sh (deprecated_register_size): Remove.

[deliverable/binutils-gdb.git] / gdb / target.h

diff --git a/gdb/target.h b/gdb/target.h
index 8796c08fb6645abcf3b65e8bda249ba4cfa85b36..7cde49b64507a4c90b441f7ee22d6e6abbe83692 100644 (file)
--- a/gdb/target.h
+++ b/gdb/target.h
@@ -189,6 +189,8 @@ enum target_object
 {
   /* AVR target specific transfer.  See "avr-tdep.c" and "remote.c".  */
   TARGET_OBJECT_AVR,
+  /* SPU target specific transfer.  See "spu-tdep.c".  */
+  TARGET_OBJECT_SPU,
   /* Transfer up-to LEN bytes of memory starting at OFFSET.  */
   TARGET_OBJECT_MEMORY,
   /* Memory, avoiding GDB's data cache and trusting the executable.
@@ -1007,31 +1009,6 @@ extern char *normal_pid_to_str (ptid_t ptid);
 #define target_extra_thread_info(TP) \
      (current_target.to_extra_thread_info (TP))
 
-/*
- * New Objfile Event Hook:
- *
- * Sometimes a GDB component wants to get notified whenever a new
- * objfile is loaded.  Mainly this is used by thread-debugging
- * implementations that need to know when symbols for the target
- * thread implemenation are available.
- *
- * The old way of doing this is to define a macro 'target_new_objfile'
- * that points to the function that you want to be called on every
- * objfile/shlib load.
-
-   The new way is to grab the function pointer,
-   'deprecated_target_new_objfile_hook', and point it to the function
-   that you want to be called on every objfile/shlib load.
-
-   If multiple clients are willing to be cooperative, they can each
-   save a pointer to the previous value of
-   deprecated_target_new_objfile_hook before modifying it, and arrange
-   for their function to call the previous function in the chain.  In
-   that way, multiple clients can receive this notification (something
-   like with signal handlers).  */
-
-extern void (*deprecated_target_new_objfile_hook) (struct objfile *);
-
 #ifndef target_pid_or_tid_to_str
 #define target_pid_or_tid_to_str(ID) \
      target_pid_to_str (ID)