Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Chris Johns <chrisj@rtems.org>
Cc: gdb-patches@sources.redhat.com, Eli Zaretskii <eliz@gnu.org>
Subject: Re: H8300 simulator on MinGW fails to compile.
Date: Thu, 14 Sep 2006 03:05:00 -0000	[thread overview]
Message-ID: <20060914030529.GA31175@nevyn.them.org> (raw)
In-Reply-To: <4508AEC7.4040803@rtems.org>

On Thu, Sep 14, 2006 at 11:22:15AM +1000, Chris Johns wrote:
> Did wonder why simulator signals needed to equated to the host signals. I 
> am still not clear why the code is like this.

No good reason.  It's historical ugliness.

> 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* ?

I'm not entirely sure any more; it's been ages since I looked at these.
I think the SIM_SIG* constants may be older than the TARGET_SIGNAL_*
constants; I don't think we need both... but I really don't know.  The
problem is that a given int variable could hold any of the three right
now.

It's a righteous mess.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-09-14  3:05 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
2006-09-14  3:05         ` Daniel Jacobowitz [this message]
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=20060914030529.GA31175@nevyn.them.org \
    --to=drow@false.org \
    --cc=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