From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: testsuite: push $arch out to targets
Date: Wed, 20 Jan 2021 12:53:16 -0700 [thread overview]
Message-ID: <8735yv5qs3.fsf@tromey.com> (raw)
In-Reply-To: <YAXNEf6Xoak+sKjB@vapier> (Mike Frysinger via Gdb-patches's message of "Mon, 18 Jan 2021 13:01:53 -0500")
Mike> as we do multibuilds, we'll have multiple ports active, so a single
Mike> variable won't cut it. moving it here and out of autotols enables
Mike> that. as we do multitarget, this will help smooth the transition as
Mike> we won't have to juggle each arch as it migrates.
I'm curious to hear about the plan here, specifically if you plan to
tackle the "gdb can only include one sim" problem.
Tom
next prev parent reply other threads:[~2021-01-20 19:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 16:09 Mike Frysinger via Gdb-patches
2021-01-18 9:52 ` Andrew Burgess
2021-01-18 18:01 ` Mike Frysinger via Gdb-patches
2021-01-20 19:53 ` Tom Tromey [this message]
2021-01-21 0:37 ` Mike Frysinger via Gdb-patches
2021-01-22 16:29 ` Tom Tromey
2021-01-23 4:35 ` Mike Frysinger via Gdb-patches
2021-01-23 17:33 ` Tom Tromey
2021-01-25 5:34 ` Mike Frysinger via Gdb-patches
2021-01-21 9:22 ` Andrew Burgess
2021-01-22 6:36 ` Mike Frysinger via Gdb-patches
2021-01-31 1:27 ` Mike Frysinger via Gdb-patches
2021-01-31 10:54 ` Andrew Burgess
2021-01-31 19:41 ` Mike Frysinger via Gdb-patches
2021-02-06 17:16 ` Mike Frysinger via Gdb-patches
2021-02-08 12:12 ` Andrew Burgess
2021-02-09 5:25 ` Mike Frysinger via Gdb-patches
2021-01-18 17:54 ` [PATCH 1/2] sim: switch top level to automake Mike Frysinger via Gdb-patches
2021-01-18 17:54 ` [PATCH 2/2] sim: testsuite: merge into toplevel automake Mike Frysinger via Gdb-patches
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=8735yv5qs3.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.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