public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/12385] cr16 sim tests can't print out "pass" message
Date: Mon, 30 Mar 2015 10:43:00 -0000 [thread overview]
Message-ID: <bug-12385-4717-GZyNW6JQIN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12385-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=12385
Mike Frysinger <vapier at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Mike Frysinger <vapier at gentoo dot org> ---
oddly, my conversion of the cr16 sim to the nrun framework also fixed the
output. this makes me think the memory handling is really wonky in this sim.
but the tests pass now, and i'm not doing anymore immediate work on it, so i
guess that's good enough ...
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2015-03-30 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 0:03 [Bug sim/12385] New: cr16 sim tests fail to link vapier at gentoo dot org
2011-06-09 4:35 ` [Bug sim/12385] " vapier at gentoo dot org
2012-03-24 21:07 ` hp at sourceware dot org
2014-03-14 0:46 ` vapier at gentoo dot org
2015-03-30 1:06 ` cvs-commit at gcc dot gnu.org
2015-03-30 1:12 ` [Bug sim/12385] cr16 sim tests can't print out "pass" message vapier at gentoo dot org
2015-03-30 10:43 ` vapier at gentoo dot org [this message]
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=bug-12385-4717-GZyNW6JQIN@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).