Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: gdb@sources.redhat.com
Cc: obrien@freebsd.org
Subject: The SPARC target
Date: Sun, 17 Aug 2003 20:48:00 -0000	[thread overview]
Message-ID: <200308172048.h7HKmlex034776@elgar.kettenis.dyndns.org> (raw)

Folks,

The SPARC target has been unmaintained for quite some time now[1]
(since november 2001) and it shows.  It doesn't compile on FreeBSD,
and running the testsuite on FreeBSD/sparc64 (after fixing it),
Solaris 2.8 and NetBSD/sparc results in hundreds of unexpected
failures with quite a few unresolved testcases.  I think the target is
bordering on (un)usability.

It's obvious what's wrong: the code is in a very bad shape.  It's
deprecation and obsoletion everywhere.  It's gotten to a point where
*I* can't make any sense out of it anymore.  Instead of fixing the old
broken code, I started implementing a FreeBSD/sparc64 target from
scratch.  Even though my work isn't finished yet, it already does a
better job than the existing SPARC target.  Of course it uses the new
unwinder framework.  I hope to be able to finish it in the coming
weeks, and check it in alongide the old code.  The new target is
64-bit only (which is fine for FreeBSD/sparc64), but I have
anticipated on writing the 32-bit bits.  When those are ready I intend
to convert all "active" SPARC targets to use the new code, replacing
the old 32-bit code with the new 32-bit code.  Unfortunately, I won't
be able to test all SPARC targets.  As a result we'll probably end up
with a number of broken SPARC targets.  Consider this message as a
HEADS UP.

Mark

[1] Maintenance only since november 2001 according to the CVS hostory
of the MAINTAINERS file.


             reply	other threads:[~2003-08-17 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-17 20:48 Mark Kettenis [this message]
2003-08-17 20:51 ` Daniel Jacobowitz
2003-08-18 17:48 Jiri Gaisler
2003-08-23 23:03 ` Mark Kettenis
2003-08-24 19:12   ` Jiri Gaisler

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=200308172048.h7HKmlex034776@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=gdb@sources.redhat.com \
    --cc=obrien@freebsd.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