From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] h8300-tdep.c: Rewrite frame code, de-deprecate, ...
Date: Fri, 29 Apr 2005 13:35:00 -0000 [thread overview]
Message-ID: <20050429133535.GB19942@nevyn.them.org> (raw)
In-Reply-To: <20050429091018.GN2572@calimero.vinschen.de>
On Fri, Apr 29, 2005 at 11:10:18AM +0200, Corinna Vinschen wrote:
> On Apr 28 15:03, Daniel Jacobowitz wrote:
> > On Thu, Apr 28, 2005 at 05:32:32PM +0200, Corinna Vinschen wrote:
> >
> > I know it's a pain, but please write a real changelog entry.
>
> Sigh, ok, see below.
Thank you.
> > > + /* Saved registers. */
> > > + CORE_ADDR saved_regs[H8300_MAX_NUM_REGS];
> > > + CORE_ADDR saved_sp;
> > > +};
> >
> > Can you use trad-frame.h instead of an array of CORE_ADDRs?
>
> I rather would not. Using the saved_regs technique is used throughout
> GDB in a couple of targets and I really don't see any advantage in using
> trad-frame.h. Actually IMHO using saved_regs directly is a lot easier
> to read for people examining the code.
It's not that it is "used throughout GDB", it's that it's a
pre-existing technique. We've been trying to migrate away from it.
Nine targets do use it, fifteen have been updated not to. Using it
improves consistency and reduces duplicated code - it would eliminate
the entire contents of h8300_frame_prev_register, for instance. If
there is something about the trad_frame interface that you find hard to
read, could you be more specific, so that we can improve the interface?
In any case, I am not interested in an argument, I've got enough of
those already :-) The patch is OK.
As followups, you should probably:
- Re-add the h8300-tdep.o to Makefile.in.
- Update the h8300 entry in MAINTAINERS to say
"--target=h8300-elf ,-Werror".
These should have been done when the target was restored, but they
were missed.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-29 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 15:33 Corinna Vinschen
2005-04-28 19:03 ` Daniel Jacobowitz
2005-04-29 9:11 ` Corinna Vinschen
2005-04-29 13:35 ` Daniel Jacobowitz [this message]
2005-04-29 14:25 ` Corinna Vinschen
2005-04-29 14:35 ` Mark Kettenis
2005-05-02 15:25 ` Corinna Vinschen
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=20050429133535.GB19942@nevyn.them.org \
--to=drow@false.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