From: fche@redhat.com (Frank Ch. Eigler)
To: bgat@billgatliff.com, gdb@sources.redhat.com
Subject: Re: How to map memory for SH simulator?
Date: Thu, 17 Jan 2002 13:50:00 -0000 [thread overview]
Message-ID: <o5elkoabpo.fsf@tooth.toronto.redhat.com> (raw)
In-Reply-To: <3C47309F.70801@cygnus.com>
cagney wrote:
> [...]
> > The sim/common family of simulators (sh, etc.) uses an alternate
> > syntax to specify additional simulated memory regions. [...]
>
> Er, are you sure about this?
Uh, good point, thanks for pointing that out. Sorry - I was thinking
of another sh simulator. There are a few stragglers in sim/*,
including the old "sh", that don't use enough common code to do this
configuration in a uniform way. This hegemony is what the sim/common,
and the later sid frameworks have been aiming to correct, but these
old ports just won't go away by themselves. :-)
Anyway, gazing at sim/sh/interp.c, there is a possibly useful "sim
set-memory-size NUMBITS" gdb command, with a similar unadorned
"sh-*-run PROGRAM NUMBITS" command line argument.
- FChE
prev parent reply other threads:[~2002-01-17 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 10:10 William A. Gatliff
2002-01-17 11:50 ` Frank Ch. Eigler
2002-01-17 12:14 ` Andrew Cagney
2002-01-17 13:50 ` Frank Ch. Eigler [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=o5elkoabpo.fsf@tooth.toronto.redhat.com \
--to=fche@redhat.com \
--cc=bgat@billgatliff.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