Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] gdbarch upkeep for FRV
Date: Wed, 13 Aug 2003 22:00:00 -0000	[thread overview]
Message-ID: <3F3AB511.2010509@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 119 bytes --]

Just a few tweaks that have fallen thru the cracks.
BTW, this target needs some upkeep WRT the new frame_info model.



[-- Attachment #2: frv --]
[-- Type: text/plain, Size: 2930 bytes --]

2003-08-13  Michael Snyder  <msnyder@redhat.com>

        * frv-tdep.c (frv_push_arguments): Use	deprecated ftype.
	(frv_saved_pc_after_call): Use	deprecated ftype.
        (stupid_useless_init_extra_frame_info): Remove orphan prototype.
	(frv_remote_translate_xfer_address): Remove.
	(frv_gdbarch_init): Use	generic_remote_translate_xfer_address.

Index: frv-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/frv-tdep.c,v
retrieving revision 1.46
diff -p -r1.46 frv-tdep.c
*** frv-tdep.c	13 Jun 2003 20:19:13 -0000	1.46
--- frv-tdep.c	13 Aug 2003 21:58:51 -0000
*************** static gdbarch_skip_prologue_ftype frv_s
*** 35,43 ****
  static gdbarch_deprecated_extract_return_value_ftype frv_extract_return_value;
  static gdbarch_deprecated_extract_struct_value_address_ftype frv_extract_struct_value_address;
  static gdbarch_frameless_function_invocation_ftype frv_frameless_function_invocation;
! static gdbarch_init_extra_frame_info_ftype stupid_useless_init_extra_frame_info;
! static gdbarch_push_arguments_ftype frv_push_arguments;
! static gdbarch_saved_pc_after_call_ftype frv_saved_pc_after_call;
  
  static void frv_pop_frame_regular (struct frame_info *frame);
  
--- 35,42 ----
  static gdbarch_deprecated_extract_return_value_ftype frv_extract_return_value;
  static gdbarch_deprecated_extract_struct_value_address_ftype frv_extract_struct_value_address;
  static gdbarch_frameless_function_invocation_ftype frv_frameless_function_invocation;
! static gdbarch_deprecated_push_arguments_ftype frv_push_arguments;
! static gdbarch_deprecated_saved_pc_after_call_ftype frv_saved_pc_after_call;
  
  static void frv_pop_frame_regular (struct frame_info *frame);
  
*************** frv_pop_frame_regular (struct frame_info
*** 920,935 ****
    flush_cached_frames ();
  }
  
- 
- static void
- frv_remote_translate_xfer_address (CORE_ADDR memaddr, int nr_bytes,
- 				   CORE_ADDR *targ_addr, int *targ_len)
- {
-   *targ_addr = memaddr;
-   *targ_len  = nr_bytes;
- }
- 
- 
  /* Hardware watchpoint / breakpoint support for the FR500
     and FR400.  */
  
--- 919,924 ----
*************** frv_gdbarch_init (struct gdbarch_info in
*** 1090,1096 ****
    set_gdbarch_function_start_offset (gdbarch, 0);
  
    set_gdbarch_remote_translate_xfer_address
!     (gdbarch, frv_remote_translate_xfer_address);
  
    /* Hardware watchpoint / breakpoint support.  */
    switch (info.bfd_arch_info->mach)
--- 1079,1085 ----
    set_gdbarch_function_start_offset (gdbarch, 0);
  
    set_gdbarch_remote_translate_xfer_address
!     (gdbarch, generic_remote_translate_xfer_address);
  
    /* Hardware watchpoint / breakpoint support.  */
    switch (info.bfd_arch_info->mach)
*************** _initialize_frv_tdep (void)
*** 1128,1131 ****
    deprecated_tm_print_insn = print_insn_frv;
  }
  
! \f
--- 1117,1120 ----
    deprecated_tm_print_insn = print_insn_frv;
  }
  
! 

             reply	other threads:[~2003-08-13 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13 22:00 Michael Snyder [this message]
2003-08-13 22:14 ` Doug Evans
2003-08-13 22:48   ` Michael Snyder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F3AB511.2010509@redhat.com \
    --to=msnyder@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox