From: David Carlton <carlton@math.stanford.edu>
To: gdb-patches@sources.redhat.com
Cc: Andrew Cagney <ac131313@redhat.com>
Subject: [rfa] delete duplicate definition of DEPRECATED_PC_IN_CALL_DUMMY
Date: Tue, 24 Dec 2002 11:29:00 -0000 [thread overview]
Message-ID: <ro1wulze1ix.fsf@jackfruit.Stanford.EDU> (raw)
config/sparc/tm-sparc.h has two identical definitions of
DEPRECATED_PC_IN_CALL_DUMMY. Here's a patch to delete one of them.
It seems obvious, but I wanted to double-check, both because I haven't
been following the dummy frame stuff too closely and because I haven't
actually yet done an all-targets build testing this patch. (That will
probably happen tonight.)
David Carlton
carlton@math.stanford.edu
2002-12-24 David Carlton <carlton@math.stanford.edu>
* config/sparc/tm-sparc.h: Delete duplicate definition of
DEPRECATED_PC_IN_CALL_DUMMY.
Index: tm-sparc.h
===================================================================
RCS file: /cvs/src/src/gdb/config/sparc/tm-sparc.h,v
retrieving revision 1.26
diff -u -p -r1.26 tm-sparc.h
--- tm-sparc.h 11 Dec 2002 02:26:38 -0000 1.26
+++ tm-sparc.h 24 Dec 2002 18:01:17 -0000
@@ -657,7 +657,6 @@ extern void sparc_print_extra_frame_info
/* Call dummy method (eg. on stack, at entry point, etc.) */
#define CALL_DUMMY_LOCATION ON_STACK
-#define DEPRECATED_PC_IN_CALL_DUMMY(pc, sp, frame_address) deprecated_pc_in_call_dummy_on_stack (pc, sp, frame_address)
/* Method for detecting dummy frames. */
next reply other threads:[~2002-12-24 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 11:29 David Carlton [this message]
2002-12-24 12:15 ` Daniel Jacobowitz
2002-12-24 14:05 ` David Carlton
2003-01-06 22:47 ` Andrew Cagney
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=ro1wulze1ix.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@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