From: Doug Evans <dje@google.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, Hans-Peter Nilsson <hp@bitrange.com>
Subject: Re: [PATCH] sim: constify watchpoint interrupt names
Date: Wed, 31 Mar 2010 01:20:00 -0000 [thread overview]
Message-ID: <e394668d1003301820u4243da2bx9204937093ade746@mail.gmail.com> (raw)
In-Reply-To: <201003301941.45755.vapier@gentoo.org>
On Tue, Mar 30, 2010 at 4:41 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> they do pass, and this reminds me of why dejagnu is so damn annoying. a
> simple `make check-sim` fails by default because the sim framework attempts to
> execute the binary on the host instead of through the sim. seems pretty dumb
> to me.
I'm guessing a patch to sim/testsuite/lib/sim-defs.exp to catch this
would be trivial.
next prev parent reply other threads:[~2010-03-31 1:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 21:49 Mike Frysinger
2010-03-30 16:19 ` Tom Tromey
2010-03-30 22:53 ` Hans-Peter Nilsson
2010-03-30 23:07 ` Mike Frysinger
2010-03-30 23:21 ` Hans-Peter Nilsson
2010-03-30 23:42 ` Mike Frysinger
2010-03-31 1:20 ` Doug Evans [this message]
2010-03-31 1:46 ` Hans-Peter Nilsson
2010-03-31 3:42 ` Mike Frysinger
2010-03-31 23:43 ` Doug Evans
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=e394668d1003301820u4243da2bx9204937093ade746@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=hp@bitrange.com \
--cc=vapier@gentoo.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