From: Mike Frysinger <vapier@gentoo.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: run: punt!
Date: Wed, 01 Apr 2015 17:13:00 -0000 [thread overview]
Message-ID: <20150401171352.GM25224@vapier> (raw)
In-Reply-To: <551BC537.4040902@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
On 01 Apr 2015 11:15, Pedro Alves wrote:
> On 04/01/2015 06:23 AM, Mike Frysinger wrote:
> > Now that all targets have been converted to nrun, we can finally punt
> > this old inconsistent interface.
>
> Great work.
>
> OOC, does this make us closer to link multiple simulators in a single
> gdb binary (for --enable-targets=all)?
it does get us closer. i've got that in mind, but i need to break down a lot
more duplicated cruft in each sim first by moving them over to common
frameworks.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-04-01 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 5:23 Mike Frysinger
2015-04-01 10:15 ` Pedro Alves
2015-04-01 17:13 ` Mike Frysinger [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=20150401171352.GM25224@vapier \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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