Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Theodore A. Roth" <troth@openavr.org>
To: gdb-patches@sources.redhat.com
Subject: [commit] [avr] remove avr_push_dummy_code method.
Date: Thu, 19 Jun 2003 19:32:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.53.0306191234190.13978@knuth.amplepower.com> (raw)

[-- Attachment #1: Type: TEXT/PLAIN, Size: 387 bytes --]

Hi,

Committed the attached.

This removes the avr_push_dummy_code function. It doesn't seem to be
needed and what I committed last night didn't return anything which
broke the -Werror build. :-(

Ted Roth

2003-06-19  Theodore A. Roth  <troth@openavr.org>

        * avr-tdep.c (avr_push_dummy_code): Delete function.
        (avr_gdbarch_init): Don't call set_gdbarch_push_dummy_code.

[-- Attachment #2: Type: TEXT/PLAIN, Size: 1534 bytes --]

2003-06-19  Theodore A. Roth  <troth@openavr.org>

	* avr-tdep.c (avr_push_dummy_code): Delete function.
	(avr_gdbarch_init): Don't call set_gdbarch_push_dummy_code.

Index: avr-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/avr-tdep.c,v
retrieving revision 1.61
diff -u -p -r1.61 avr-tdep.c
--- avr-tdep.c	19 Jun 2003 08:09:54 -0000	1.61
+++ avr-tdep.c	19 Jun 2003 19:22:10 -0000
@@ -1128,16 +1128,6 @@ avr_unwind_dummy_id (struct gdbarch *gdb
   return frame_id_build (avr_make_saddr (base), frame_pc_unwind (next_frame));
 }
 
-static CORE_ADDR
-avr_push_dummy_code (struct gdbarch *gdbarch,
-                     CORE_ADDR sp, CORE_ADDR funaddr, int using_gcc,
-                     struct value **args, int nargs,
-                     struct type *value_type,
-                     CORE_ADDR *real_pc, CORE_ADDR *bp_addr)
-{
-  fprintf_unfiltered (gdb_stderr, " ----->>>>  push_dummy_code\n");
-}
-
 /* When arguments must be pushed onto the stack, they go on in reverse
    order.  The below implements a FILO (stack) to do this. */
 
@@ -1357,7 +1347,6 @@ avr_gdbarch_init (struct gdbarch_info in
 
   set_gdbarch_call_dummy_address (gdbarch, avr_call_dummy_address);
   set_gdbarch_push_dummy_call (gdbarch, avr_push_dummy_call);
-  set_gdbarch_push_dummy_code (gdbarch, avr_push_dummy_code);
 
   set_gdbarch_address_to_pointer (gdbarch, avr_address_to_pointer);
   set_gdbarch_pointer_to_address (gdbarch, avr_pointer_to_address);

             reply	other threads:[~2003-06-19 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 19:32 Theodore A. Roth [this message]
2003-06-19 20:15 ` Andrew Cagney
2003-06-19 20:21   ` Theodore A. Roth

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=Pine.LNX.4.53.0306191234190.13978@knuth.amplepower.com \
    --to=troth@openavr.org \
    --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