From: Chris Johns <chrisj@rtems.org>
To: gdb-patches@sources.redhat.com
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: H8300 simulator on MinGW fails to compile.
Date: Thu, 14 Sep 2006 01:22:00 -0000 [thread overview]
Message-ID: <4508AEC7.4040803@rtems.org> (raw)
In-Reply-To: <20060913203009.GA21009@nevyn.them.org>
Daniel Jacobowitz wrote:
> First, a minor point: your patch was reversed, deleting instead
> of adding. New file second on the diff command line.
Oops. I will not post again until your second point is resolved.
>
> On Thu, Sep 14, 2006 at 06:10:08AM +1000, Chris Johns wrote:
>> ../../../gdb-6.5/sim/h8300/compile.c: In function `sim_resume':
>> ../../../gdb-6.5/sim/h8300/compile.c:1942: error: `SIGBUS' undeclared
>> (first use in this function)
>> ../../../gdb-6.5/sim/h8300/compile.c:1942: error: (Each undeclared
>> identifier is reported only once
>> ../../../gdb-6.5/sim/h8300/compile.c:1942: error: for each function it
>> appears in.)
>> make[3]: *** [compile.o] Error 1
>
> Some work has been done to reduce the use of host signal numbers in the
> simulator. Rather than adding more bandaids, we need to do more to
> switch to either the SIM_* or TARGET_SIGNAL_* constants. The host's
> numbers just aren't relevant.
Did wonder why simulator signals needed to equated to the host signals. I am still not
clear why the code is like this.
>
> Unfortunately all the code is somewhat tangled in multiple sims.
>
I see what you mean.
The TARGET_SIGNAL_* shows up in the ppc, d10v, and arm sims. The host type SIG* such as
SIGBUS appear to be in most of the sims.
Is the solution to change sim-signal.c to use TARGET_SIGNAL_* and then change the effected
sim files to SIM_SIG* ?
Regards
Chris
next prev parent reply other threads:[~2006-09-14 1:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 12:33 Chris Johns
2006-09-13 16:55 ` Eli Zaretskii
2006-09-13 20:10 ` Chris Johns
2006-09-13 20:30 ` Daniel Jacobowitz
2006-09-14 1:22 ` Chris Johns [this message]
2006-09-14 3:05 ` Daniel Jacobowitz
2006-09-14 23:43 ` Chris Johns
2006-09-16 3:53 ` Daniel Jacobowitz
2006-09-19 1:20 ` Chris Johns
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=4508AEC7.4040803@rtems.org \
--to=chrisj@rtems.org \
--cc=eliz@gnu.org \
--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