Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: Multi-arch only GDB 6.0 ....
Date: Thu, 18 Apr 2002 18:15:00 -0000	[thread overview]
Message-ID: <20020418211607.A16989@nevyn.them.org> (raw)
In-Reply-To: <3CBF6BEF.2050003@cygnus.com>

On Thu, Apr 18, 2002 at 08:59:27PM -0400, Andrew Cagney wrote:
> 
> >It's a nice idea, but can we really ditch all the non-multi-arch targets?
> >I think you filed bugs about them all at one point; could you give an
> >exact list of the targets that would be going?
> 
> Lets turn the question around.
> 
> Why should GDB 6.0 retain support non-multi-arch targets?  If someone 
> needs to debug a non-multi-arch target they can download GDB 5.x.

Let me be clearer; I think there are some targets we need to allow time
to fix ourselves based on userbase, rather than on maintained-ness.  I
would wager that GDB on Alpha has a fair number of users, and it seems
to work relatively well.  If they prove unreasonably difficult to
multi-arch, well, that's a different story.

> For current status, see the file src/gdb/MAINTAINERS.  Hmm, the ARM 
> entry is out-of-date!  The ones marked as ``OBSOLETE candidate'' are 
> first up.
> 
> >I'm stuck maintaining GDB for Debian right now.  In our current
> >release, that's 11 architectures.  I think that at the least Sparc,
> >Alpha, and m68k are non-multi-arch (and HPPA is non-contributed, but
> >there's nothing I can do about that...).  We may be able to talk David
> >into cleaning up Sparc, but at the other two are also still in active
> >use.  I think that we need to allow more time in order to get as many
> >targets as possible converted over - I'll do the two I mentioned myself
> >if no one else has time, but it'll take a while.
> 
> The SPARC is multi-arch, Alpha is WIP, m68k had an expression of 
> interest, HP/UX is typically broken.

Most of SPARC is only multiarch if it snuck in with David's cleanups
recently.  A day-old tree:

tm-sp64.h:#define GDB_MULTI_ARCH GDB_MULTI_ARCH_PARTIAL
tm-sp64linux.h:#define GDB_MULTI_ARCH 0
tm-sun4sol2.h:#define GDB_MULTI_ARCH GDB_MULTI_ARCH_PARTIAL

Someone was working on HP/UX just a little while ago - Jeff Law, I
think.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-04-19  1:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 17:08 Andrew Cagney
2002-04-18 17:15 ` Daniel Jacobowitz
2002-04-18 17:59   ` Andrew Cagney
2002-04-18 18:15     ` Daniel Jacobowitz [this message]
2002-04-18 18:39       ` Andrew Cagney
2002-04-19  0:26     ` Eli Zaretskii
2002-04-19  2:35     ` Andreas Schwab
2002-04-19  7:22       ` Elena Zannoni
2002-04-19  8:01         ` Andrew Cagney

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=20020418211607.A16989@nevyn.them.org \
    --to=drow@mvista.com \
    --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