Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: Corinna Vinschen <vinschen@redhat.com>
Subject: Re: [PATCH] h8300-tdep.c: Drop xxx_register_byte and xxx_virtual_register_type
Date: Fri, 13 Jun 2003 13:21:00 -0000	[thread overview]
Message-ID: <3EE9CFEE.3000508@redhat.com> (raw)
In-Reply-To: <20030613081159.GA11176@cygbert.vinschen.de>

> -static int
> -h8300h_register_byte (int regno)
> -{
> -  if (regno < 0 || regno >= NUM_REGS)
> -    internal_error (__FILE__, __LINE__,
> -		    "h8300_register_byte: illegal register number %d", regno);
> -  else
> -    return regno * h8300h_reg_size;
> -}
> -
>  static struct type *
> -h8300_register_virtual_type (int regno)
> +h8300_register_type (struct gdbarch *gdbarch, int regno)
>  {
>    if (regno < 0 || regno >= NUM_REGS)
>      internal_error (__FILE__, __LINE__,
> -		    "h8300_register_virtual_type: illegal register number %d",
> +		    "h8300_register_type: illegal register number %d",
>  		    regno);
>    else
>      {

A word of caution here to would be updaters.  Before dropping 
register_byte make certain that its removal doesn't modify the register 
cache's layout (use maint print registers).

The MIPS, for instance, would change radically, if register byte is 
removed - it needs other significant surgery.

The problem here is that REGISTER_BYTE also defines the [Gg] remote 
protocol layout.  Things to do today includes adds a comment warning of 
this.

Andrew



      reply	other threads:[~2003-06-13 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13  8:12 Corinna Vinschen
2003-06-13 13:21 ` 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=3EE9CFEE.3000508@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vinschen@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