Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marko Mlinar <markom@opencores.org>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: OC?
Date: Wed, 29 Jan 2003 06:54:00 -0000	[thread overview]
Message-ID: <200301290803.13751.markom@opencores.org> (raw)
In-Reply-To: <3E36DDBD.9000108@redhat.com>

On Tuesday 28 January 2003 20:45, Andrew Cagney wrote:
> > Hi Andrew!
> >
> >> Turns out this has been done.
> >>
> >> > We have also problems with registers. You were saying something that
> >> > we should move all the registers (we have 8k+ registers with generated
> >> > names) into the temporary storage (I hope all these won't get cached
> >> > in the host...).
>
> 8k * 8 bytes ~= 64k.
>
> Either that all lives in the text segment, or it is only allocated when
> all the names are asked for.

Andrew,

I was referring more to register transfer. Most of the registers should not be 
chached at all -- the value read from these special purpose registers (SPRs) 
can differ in time/access. Some registers may also have clear-after-read, 
FIFO implemented or any other obscure functionality.

It would be nice if all names would be generated, instead of storing their 
names, however I suppose nobody with our target will complain about high 
memory usage.

Another problem is with printing it out and displaying. Unfortunatelly I don't 
know how exaclty the remote debuggers work (we mostly use DDD), but if they 
try to read all registers when e.g. they reach breakpoint -- it will break 
the target (because e.g. clear-after-read). And besides it may take a while 
to load them all in.

> >> Yes.  A gui for instance will likely want access to all names at once.
> >
> > I tried to fix this issue, but there were not enough documentation nor
> > such targets for me to dig through. Is it possible that you (or somebody
> > else) change this please?
>
> I'm not sure what the problem is.  Just wrap the current code in
> something that maintains a table of previously returned names.

I don't know a lot of internals, which are common knowledge for most here, and 
I didn't know if my solutions would solve all above issues.

thanks,
Marko


  reply	other threads:[~2003-01-29  6:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 14:27 OC? Andrew Cagney
2002-12-11  6:38 ` OC? Marko Mlinar
2003-01-14 16:09   ` OC? Andrew Cagney
2003-01-15  8:22     ` OC? Marko Mlinar
2003-01-28 19:45       ` OC? Andrew Cagney
2003-01-29  6:54         ` Marko Mlinar [this message]
2003-01-29 15:31           ` OC? Andrew Cagney

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=200301290803.13751.markom@opencores.org \
    --to=markom@opencores.org \
    --cc=ac131313@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