Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: Mingw GDB build fails for M16C target
Date: Wed, 29 Apr 2009 20:27:00 -0000	[thread overview]
Message-ID: <20090429132702.57adecb3@redhat.com> (raw)
In-Reply-To: <20090429200124.GA961@caradoc.them.org>

On Wed, 29 Apr 2009 16:01:24 -0400
Daniel Jacobowitz <drow@false.org> wrote:

> > If you're asking why I don't simply copy sim_signal_to_target for
> > use in m32c/gdb-if.c, that's because the m32c sim doesn't use the
> > SIM_SIGfoo constants that common/sim-signal.c uses.  It does bother me
> > though that m32c_signal_to_target() uses hardcoded constants like 4,
> > 5, 10, 11, etc.  I suspect it was done this way because including the
> > correct newlib header file (without conflict with certain system
> > headers) was difficult.  That's just a guess though.
> 
> I was actually asking about sim_signal_to_host, since this was
> m32c_signal_to_host.  The sim_ version uses SIGILL, SIGTRAP, etc.

Wow, did I guess wrong.

My patch changes the name from m32c_signal_to_host() to
m32c_signal_to_target() and switches from use of host-based numbers
to target-specific numbers.

> Yes... I don't think any of the conversion routines that use host
> numbers should be there.  I'm not feeling ambitious enough to remove
> them from all sims, but perhaps you can get just m32c?

Yes, I have done this.  See above.

Kevin


  reply	other threads:[~2009-04-29 20:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <82C3BC9106BCE149B63464D79D0A22FD0A68110C@sohm.kpit.com>
2009-04-28 22:57 ` Kevin Buettner
2009-04-29  2:35   ` Daniel Jacobowitz
2009-04-29 19:51     ` Kevin Buettner
2009-04-29 20:01       ` Daniel Jacobowitz
2009-04-29 20:27         ` Kevin Buettner [this message]
2009-04-29 20:33           ` Daniel Jacobowitz
2009-05-08 22:57   ` Kevin Buettner

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=20090429132702.57adecb3@redhat.com \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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