From: Mark Kettenis <kettenis@chello.nl>
To: jiri@gaisler.com
Cc: gdb@sources.redhat.com
Subject: Re: The SPARC target
Date: Sat, 23 Aug 2003 23:03:00 -0000 [thread overview]
Message-ID: <868ypkt1sd.fsf@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: Jiri Gaisler's message of "Mon, 18 Aug 2003 19:49:29 +0200"
Jiri Gaisler <jiri@gaisler.com> writes:
> Mark Kettenis wrote:
>
> > 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.
>
>
> I would like to point out that the sparc port works quite well
> for embedded (o/s unaware) 32-bit targets, at least up to gdb-5.3 .
> There are some (minor) quirks with stack unwinding to form the
> function backtrace, but overall it makes a good job. If you make
> a new (64-bit) backend, could the old 32-bit backend remain, at
> least the O/S independent parts?
Well, most of the bitrot seems to have taken place after the 5.3
release. So I'm not at all confident that it still works to your
satisfaction. I'm working on the 32-bit SPARC target now, and I'm
pretty confident that I can get it in a shape where it works better
than GDB 5.3. It's not until then that I'll replace the old code with
my new implementation.
Just out of curiosity. What's the --target you use to configure the
GDB you're using to debug your embedded system?
Mark
next prev parent reply other threads:[~2003-08-23 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 17:48 Jiri Gaisler
2003-08-23 23:03 ` Mark Kettenis [this message]
2003-08-24 19:12 ` Jiri Gaisler
-- strict thread matches above, loose matches on Subject: below --
2003-08-17 20:48 Mark Kettenis
2003-08-17 20:51 ` Daniel Jacobowitz
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=868ypkt1sd.fsf@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb@sources.redhat.com \
--cc=jiri@gaisler.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