Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stephane Carrez <Stephane.Carrez@worldnet.fr>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: RFC:  --enable-targets=<list>
Date: Tue, 17 Jul 2001 15:18:00 -0000	[thread overview]
Message-ID: <3B54BAAD.33F491B9@worldnet.fr> (raw)
In-Reply-To: <3B520689.1000300@cygnus.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]

Hi!

Andrew Cagney a écrit :
> 
> Hello,
> 
> I'm getting ready to commit a patch (raw draft attached) that makes it
> possible to build a GDB that contains several orthogonal target
> architectures.  Not sure what happens when you use it yet :-)
> 

Apart from the simulator, there will be a problem with the tm_print_insn
function.  There is only one, and the first _init_tdep that is called
will install its own.

I tried to have a look some day and see if we could use the opcodes generic
entry point but I stopped because there was some more work with some targets.


> Anyway, I'm trying to take a softly softly approach.  The attatched
> configury tweek tries to do the right thing (multi-arch when possible)
> and warn the user when something isn't possible.  The alternative would
> be to simply fail.  Thoughts?
> 
> Until someone comes up with something better, GDB will link in just the
> primary target's simulator.
> 
> As a preliminary change, I intend updating all the pure- multi-arch
> targets so that they set gdb_tdepfiles in configure.tgt instead of
> TDEPFILES=... in *.mt.  The patch currently interprets that to mean a
> multi-arch target, perhaphs I shouldn't do that?
> 
I'll be happy to test that.

	Stephane


      parent reply	other threads:[~2001-07-17 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-15 14:10 Andrew Cagney
2001-07-16  1:29 ` Eli Zaretskii
2001-07-16  8:07   ` Andrew Cagney
2001-07-17 15:18 ` Stephane Carrez [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=3B54BAAD.33F491B9@worldnet.fr \
    --to=stephane.carrez@worldnet.fr \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.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