From: Nick Clifton <nickc@cambridge.redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Add support for target switches in simulator
Date: Fri, 17 May 2002 01:58:00 -0000 [thread overview]
Message-ID: <m3n0uz40dg.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <200205161624.RAA15198@cam-mail2.cambridge.arm.com>
Hi Guys,
Answers to comments on my patch submission:
> > I would like permission to apply the following patch. It adds
> > the ability for simulator backends to parse their own command
> > line switches, thus creating target specific simulator options.
> Frank Ch. Eigler writes:
>
> How does this proposed facility compare to that provided by
> sim/common/sim-options*?
It is a similar kind of thing accept that it has two advantages:
* It works for simulators that do not use sim-common.[ch] (such as
the ARM simualtor).
* It isolates all of the target specific code in the target specific
subdirectories, and just has a very small intrusion into the
generic code. (Unlike say the SIM_H8300 option).
> > I have not worked out how this feature would be accessed from
> > GDB. My guess is that the switches could be added to the
> > arguments passed via sim_open(), but how would a GDB user tell
> > GDB to add these switches ?
> Richard Earnshaw <rearnsha@arm.com> writes:
> Hmm, I thought there was already a way to tell the simulator what
> amount of memory to use.
So did I, but looking through the GDB sources I do not see a place
where it is used.
> Couldn't a similar method be employed.
That method is specific to setting the memory size - it uses a
simulator/debugger interface call specifically set up for the
purpose. I looked for the function - sim_size() - and found it being
used by the run program but not by GDB. I am puzzled.
Anyway the point here is that setting the memory size appears to be a
specific API function and I want a generic method to set any kind of
target specific option.
> From: Michael Snyder <msnyder@redhat.com>
From memory, don't you do something like:
(gdb) target sim xxx=yyy
Yup that works - thanks Michael.
I have now updated my ARM SIM patch so that it will work using this
interface. So if the common sim part can be approved then we will
have a complete method for controlling SWI emulation in the ARM
simulator.
Cheers
Nick
PS. I will post the arm sim parts of the patch to this list shortly.
next prev parent reply other threads:[~2002-05-17 8:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 3:09 Add support for RedBoot SWIs to ARM Simulator Nick Clifton
2002-05-09 3:22 ` Richard Earnshaw
2002-05-09 4:00 ` Nick Clifton
2002-05-09 4:11 ` Richard Earnshaw
2002-05-16 9:16 ` Add support for target switches in simulator Nick Clifton
2002-05-16 9:25 ` Richard Earnshaw
2002-05-17 1:58 ` Nick Clifton [this message]
2002-05-17 5:37 ` Richard Earnshaw
2002-05-17 6:46 ` Nick Clifton
2002-05-17 10:17 ` Andrew Cagney
2002-05-17 7:33 ` Frank Ch. Eigler
2002-05-17 10:29 ` Andrew Cagney
2002-05-16 9:36 ` Frank Ch. Eigler
2002-05-16 11:08 ` Michael Snyder
2002-05-17 11:32 ` Andrew Cagney
2002-05-20 6:11 ` Nick Clifton
2002-05-20 7:12 ` Andrew Cagney
2002-05-20 7:19 ` Richard Earnshaw
2002-05-20 7:26 ` Nick Clifton
2002-05-09 7:35 ` Add support for RedBoot SWIs to ARM Simulator Frank Ch. Eigler
2002-05-20 7:49 Add support for target switches in simulator Nick Clifton
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=m3n0uz40dg.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@cambridge.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