Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joern Rennecke <joern.rennecke@superh.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Unreviewed patches
Date: Fri, 12 Jul 2002 05:47:00 -0000	[thread overview]
Message-ID: <3D2EC4B3.FDDB3D47@superh.com> (raw)
In-Reply-To: <15662.14806.918730.224362@localhost.redhat.com>

Elena Zannoni wrote:
> For the gdb sh-tdep.c part, I have a few comments.
> There is no need for a prototype. I removed all of those a few months back.

Ok, I'll place the new function so that it needs no prototype.
But you have to keep in mind that that makes the call graph more
rigid, unless you like to move code around a lot.

> You should just move the new function to before the gdbarch_init one.
> Instead of adding another enum, you should use
> 
>   struct gdbarch_tdep *tdep = gdbarch_tdep (current_gdbarch);
>  and then
>   tdep-><...>_REGNUM
> 
> If you need new register numbers for the dsp case, just add
> them to the tdep structure.

I think the stashing of constants into the tdep structure is basically
wrong.  You separate the register names arrays from the literals
that describe their positions, and you replicate the literals
up to four times.  The tdep structure and the sh_gdbarch_init
function are so large that you have lost track of the things that
really belong in tdep, like sh_show_regs, skip_prologue_hard_way,
and do_pseudo_register.  If you look at other gdb ports, you'll
see that they put only variable stuff in tdep, and use enums
for constants.  The sh gdb register naming scheme also doesn't
scale well, the names are again duplicated multiple times.
	
I have a scheme that names each register just once, and enumerates
it only once - in an enum, of course.  But I thought we should first
sort out the simulator <-> gdb and gcc -> gdb interfaces before we
start on the gdb internals.
	
-- 
--------------------------
SuperH
2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ
T:+44 1454 462330


  reply	other threads:[~2002-07-12 11:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-01  6:55 Joern Rennecke
2002-07-01  8:47 ` Elena Zannoni
2002-07-01 10:10   ` Joern Rennecke
2002-07-01 14:24     ` Elena Zannoni
2002-07-01 15:01       ` Joern Rennecke
2002-07-02 12:32         ` Elena Zannoni
2002-07-03 13:49           ` Joern Rennecke
2002-07-12  4:59             ` Elena Zannoni
2002-07-12  5:47               ` Joern Rennecke [this message]
2002-07-12  8:23                 ` Andrew Cagney
2002-07-17 11:30                   ` Joern Rennecke
2002-07-17 13:04                     ` Andrew Cagney
2002-08-05  6:47                     ` Elena Zannoni
2002-07-12 11:36                 ` Elena Zannoni
  -- strict thread matches above, loose matches on Subject: below --
2007-10-11 14:51 Kazu Hirata
2007-10-04 12:04 Kazu Hirata
2003-01-30  6:03 Kazu Hirata
2003-01-31  2:36 ` Michael Snyder
2003-01-31  4:54   ` Kazu Hirata
2003-02-01  1:27     ` Michael Snyder
2003-02-01  3:23       ` Kazu Hirata
2003-02-03 20:30         ` Michael Snyder
2003-02-03 23:30           ` Kazu Hirata
2003-02-05 22:41             ` Michael Snyder
2003-01-17  4:33 Kazu Hirata
2002-06-19 14:29 Joern Rennecke

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=3D2EC4B3.FDDB3D47@superh.com \
    --to=joern.rennecke@superh.com \
    --cc=ezannoni@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