From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Remove D10V-specific code from arch-independent modules
Date: Wed, 04 Jul 2001 22:43:00 -0000 [thread overview]
Message-ID: <3B43FE67.5000106@cygnus.com> (raw)
In-Reply-To: <20010629000735.132405E9CB@zwingli.cygnus.com>
Jim,
Some immediate comments:
--
> + struct type *code_ptr_type;
should this be a builtin_type? GDB has:
> /* Address/pointer types: */
> /* (C) Language pointer type. Some target platforms use an implicitly
> {sign,zero} -extended 32 bit C language pointer on a 64 bit ISA. */
> extern struct type *builtin_type_ptr;
I think having:
extern struct type *builtin_type_data_ptr;
extern struct type *builtin_type_{func,insn,???}_ptr;
would make more sense. It would also eliminate the need for the hack:
> ! /* We can't create this type until the D10V gdbarch object has been
> ! made current, or else the size will be wrong. This means we
> ! can't initialize it in d10v_gdbarch_init. So we do it here, the
> ! first time we need it. */
> ! if (! tdep->code_ptr_type)
> ! tdep->code_ptr_type
> ! = lookup_pointer_type (lookup_function_type (builtin_type_void));
> !
--
The s/D10V_MAKE_IADDR/d10v_make_iaddr/ et.al. applied to d10v-tdep.c can
go straight in as an obvious fix. This should make the final patch a
lot smaller :-)
--
The convert to/from virtual/raw register functions are borderline
deprecated. They are being replaced by the much simpler functions
gdbarch_register_{read,write}. If, for the d10v, those conversion
functions are being eliminated then I'd just delete them.
--
Once I've got a more concrete feel for the change (the examples) I'll go
back through this.
Andrew
next prev parent reply other threads:[~2001-07-04 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 17:06 Jim Blandy
2001-07-04 22:43 ` Andrew Cagney [this message]
2001-07-05 15:38 ` Jim Blandy
2001-07-05 15:58 ` Andrew Cagney
2001-07-09 20:03 David Taylor
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=3B43FE67.5000106@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.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