Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Regcache changes broke MIPS
Date: Sun, 09 Dec 2001 19:09:00 -0000	[thread overview]
Message-ID: <3C142777.9080908@cygnus.com> (raw)
In-Reply-To: <20011209183304.A15018@nevyn.them.org>

> Hmm, doctor the patient is worse than we thought (and how ironic, this 
>> one is my target).
>> 
>> Briefly, the MIPS still defines certain methods (REGISTER_RAW_SIZE() at 
>> least) as macro's mapped onto functions instead of true multi-arch 
>> methods.  That is why they are being called when they shouldn't.
>> 
>> I came up with a patch that fixed just REGISTER_RAW_SIZE() but that 
>> didn't fix it - suspect I need to find more.
> 
> 
> I think I follow.  Do you actually currently build the register cache
> with dummy values (on a multiarch target) and then rebuild it after
> gdbarch is initialized?


I fixed REGISTER_RAW_SIZE() and it died in what appeared to be 
REGISTER_BYTE() .....

At present the architecture gets built three times (!!!):

	o	dummy architecture

	o	default architecture

	o	executables architecture

The first one goes, once the non multi-arch targets are removed.


> It seems like there should be a way to register a post-gdbarch,
> non-multi-arch-target init function to avoid this.


That is hopefully unnecessary.  Just need to convert a few more MIPS macros.

	Andrew




      reply	other threads:[~2001-12-10  3:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-08 20:41 Daniel Jacobowitz
2001-12-09 13:59 ` Andrew Cagney
2001-12-09 14:52   ` Andrew Cagney
2001-12-09 15:34     ` Daniel Jacobowitz
2001-12-09 19:09       ` 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=3C142777.9080908@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb@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