From: Andrew Cagney <ac131313@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Get rid of DEPRECATED_PC_IN_CALL_DUMMY in i386-tdep.c
Date: Thu, 12 Dec 2002 16:19:00 -0000 [thread overview]
Message-ID: <3DF92473.9020908@redhat.com> (raw)
In-Reply-To: <200212121047.gBCAlFr08321@pc960.cambridge.arm.com>
> I was looking at the DEPRECATED_PC_IN_CALL_DUMMY use in arm-tdep.c last
> night and I came to the conclusion that I hadn't a clue what I was
> supposed to do to remove it. Is all the code dead? Does it all need
> translating into pc_in_dummy_frame? etc, etc.
>
> Could I suggest that when we deprecate a call some documentation is added
> *somewhere* saying what sort of things (I accept that it might not be a
> trivial substitution) should be used to replace existing deprecated code.
> One possible place would be in gdbarch.sh, though that's constrained a
> bit. doc/deprecated.texinfo?
I try to leave a comment with the doco but keep missing them :-(
> something of the form
>
> ->> DEPRECATED_PC_IN_CALL_DUMMY: Replace with calls to XXX or YYY as
> appropriate using the new ZZZ methods for doing wibble.
>
> This would then be a key for things to look up in the manual (the new
> methods are documented, right?) to understand how it's all supposed to
> work.
Things to do during my summer holidays is write said doco (that and the
register cache).
As for deprecated_pc_in_call_dummy. It should be dead, not needed,
redundant, superfulious[sp], irrelevant, gone to meet its creator,
ceased to be, .... the only time GDB should call the tdep code is on a
normal frame.
However, because I've not committed the changes that re-order frame
initialization to use the sequence:
frame_pc_unwind()
frame_id_unwind()
create frame
The arm may in some way still depend on that macro. If it does I'd like
to know.
Andrew
prev parent reply other threads:[~2002-12-13 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 6:56 Mark Kettenis
2002-12-11 9:38 ` Andrew Cagney
2002-12-12 3:06 ` Richard Earnshaw
2002-12-12 16:19 ` Andrew Cagney [this message]
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=3DF92473.9020908@redhat.com \
--to=ac131313@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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