Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Subject: [rfc] [0/9] Multi-target support
Date: Fri, 26 Oct 2007 01:15:00 -0000	[thread overview]
Message-ID: <200710260114.l9Q1EtUT003048@d12av02.megacenter.de.ibm.com> (raw)

Hello,

as promised, here's a set of patches to provide the --enable-targets=
configure option, allowing to support multiple (remote) targets within
a single GDB executable.

The basic implementation idea is simple: now that DEPRECATED_TM_FILE
is no longer in use, the only remaining settings provided by target-
specific makefile fragments *.mt are TDEPFILES, SIM, and SIM_OBS.

The patch series moves this information from the makefile fragments
into configure.tgt itself (removing the then-obsolete concept of
per-target makefile fragments in the process).

Once we have the list of target-dependent object files available in
configure.tgt, we can simply execute that script multiple times,
once for every desired target configuration, and simply accumulate
the total set of needed object files to support all of them.

Note that other target-specific information, in particular whether
to build a simulator or the gdbserver, remains determined by the
"master" target (specified via --target), not --enable-targets.
Also, only the master target can be used as native configuration
(if applicable).  All other targets are supported as remote or
core file targets only.

I'm aware of one bug that still needs to be fixed: "info set"
crashes as show_mipsfpu_command unconditionally refers to
gdbarch_tdep (current_gdbarch), and assumes it to be formatted
as defined in mips-tdep.c.  This is of course no longer guaranteed
to be the case ...   It is certainly possible that other problems
of that sort still lurk.

I'd appreciate any feedback on the approach, and testers of
various combinations of host vs. --enable-targets=... settings
would certainly be welcome.

I've tested the full patch set with no regressions (except for
the mips issue above) with both a regular build and an 
--enable-targets=all build on each of powerpc64-linux, 
s390-ibm-linux, s390x-ibm-linux, and amd64-linux.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


             reply	other threads:[~2007-10-26  1:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26  1:15 Ulrich Weigand [this message]
2007-10-26  7:19 ` Daniel Jacobowitz
2007-10-30 21:54 ` [rfc] [0/9] Multi-target support: Fix show_mipsfpu_command crash Ulrich Weigand
2007-11-17  1:08 ` [rfc] [0/9] Multi-target support Ulrich Weigand
2007-11-19 10:14   ` Pierre Muller
2007-11-19 11:38     ` Ulrich Weigand
2007-11-19 16:35       ` Pierre Muller
2007-11-19 17:24         ` Ulrich Weigand
2007-11-19 17:28           ` Daniel Jacobowitz
2007-11-20 22:17             ` Ulrich Weigand
2007-11-20 22:23         ` [rfc/rft] --enable-targets=all with 32-bit BFD Ulrich Weigand
2007-11-21  1:01           ` Pedro Alves
2007-11-26 15:30             ` Ulrich Weigand
2007-11-27  3:00               ` Pedro Alves
2007-11-27 17:08                 ` Ulrich Weigand

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=200710260114.l9Q1EtUT003048@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.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