From: "Christian Jönsson" <c.christian.joensson@telia.com>
To: Tom Tromey <tromey@redhat.com>
Cc: java@gcc.gnu.org
Subject: gcc-3.1 2002-04-03 libjava failures on sparc-linux?
Date: Fri, 05 Apr 2002 09:29:00 -0000 [thread overview]
Message-ID: <20020405172653.GA3118@j-son.org> (raw)
Hej Tom.
I am test building the gcc-3.1 prereleases on sparc-linux, n.b.,
debian, no more sparc support from redhat...
The results of the testsuite is getting better and better, but libjava
still has a lot of failures.
Could you perhaps elaborate a little on what you think might be the
causes behind these failures?
I know that the support for sparc32 in the linux kernel is lagging,
there might be such problems. And, it's a 2.2.x kernel I'm running,
2.4.x is not stable enough yet (ever?) on smp sun4m.
Cheers,
/ChJ
This was on a Debian Woody (test release) sun4m system using
binutils 2.12.90.0.1-1
dejagnu 1.4.2-1.1
gcc 2:2.95.4-14 (Debian prerelease)
gcc-2.95 1:2.95.4-5 (Debian prerelease)
kernel-image-2.2.20-sun4dm-smp 9
libc6 2.2.5-3 (now libc6-2.2.5-4)
next reply other threads:[~2002-04-05 17:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 9:29 Christian Jönsson [this message]
2002-04-05 9:50 ` Christian Jönsson
2002-04-08 13:15 ` Tom Tromey
2002-04-08 14:27 ` Christian Jönsson
2002-04-09 9:48 ` Christian Jönsson
2002-04-09 15:02 ` Tom Tromey
2002-04-09 23:39 Boehm, Hans
2002-04-10 5:17 ` Christian Jönsson
2002-04-10 12:21 Boehm, Hans
2002-04-15 0:13 ` Christian Jönsson
2002-04-15 20:03 Boehm, Hans
2002-04-15 23:08 ` Christian Jönsson
2002-04-16 3:31 ` Christian Jönsson
2002-04-16 16:33 ` Tom Tromey
2002-04-17 0:28 ` Christian Jönsson
2002-04-17 1:05 ` Christian Jönsson
2002-04-17 10:19 Boehm, Hans
2002-04-17 10:54 ` Christian Jönsson
2002-04-17 13:00 ` Christian Jönsson
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=20020405172653.GA3118@j-son.org \
--to=c.christian.joensson@telia.com \
--cc=java@gcc.gnu.org \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).