From: "Christian Jönsson" <christian@j-son.org>
To: "Boehm, Hans" <hans_boehm@hp.com>
Cc: Tom Tromey <tromey@redhat.com>, java@gcc.gnu.org
Subject: Re: gcc-3.1 2002-04-03 libjava failures on sparc-linux?
Date: Wed, 17 Apr 2002 13:00:00 -0000 [thread overview]
Message-ID: <20020417175437.GA909@j-son.org> (raw)
In-Reply-To: <40700B4C02ABD5119F000090278766443BF1EE@hplex1.hpl.hp.com>
On Wed, Apr 17, 2002 at 09:46:38AM -0700, Boehm, Hans wrote:
> I think this part of the patch should be checked into both the branch and
> trunk. If in parallel someone else could try this on other Linux/SPARC
> machines, that would help to verify that the main stack base is always
> correctly reported in /proc. But the current code is very hard to defend,
> at least given the fact that it isn't always correct.
I have now also tested that building and running *gctest* (from gcc-3.1 built
under sparc32/linux-2.2.20 SMP) works under sparc32/linux-2.4.19-pre7 SMP.
Cheers,
/ChJ
next prev parent reply other threads:[~2002-04-17 17:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 10:19 Boehm, Hans
2002-04-17 10:54 ` Christian Jönsson
2002-04-17 13:00 ` Christian Jönsson [this message]
-- strict thread matches above, loose matches on Subject: below --
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-10 12:21 Boehm, Hans
2002-04-15 0:13 ` Christian Jönsson
2002-04-09 23:39 Boehm, Hans
2002-04-10 5:17 ` Christian Jönsson
2002-04-05 9:29 Christian Jönsson
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
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=20020417175437.GA909@j-son.org \
--to=christian@j-son.org \
--cc=hans_boehm@hp.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).