From: "Christian Jönsson" <christian@j-son.org>
To: Tom Tromey <tromey@redhat.com>
Cc: "Boehm, Hans" <hans_boehm@hp.com>, java@gcc.gnu.org
Subject: Re: gcc-3.1 2002-04-03 libjava failures on sparc-linux?
Date: Wed, 17 Apr 2002 01:05:00 -0000 [thread overview]
Message-ID: <20020417072827.GA19253@j-son.org> (raw)
In-Reply-To: <20020417072236.GA5511@j-son.org>
On Wed, Apr 17, 2002 at 09:22:36AM +0200, chj wrote:
> On Tue, Apr 16, 2002 at 10:08:45AM -0600, Tom Tromey wrote:
> > >>>>> "ChJ" == Christian Jönsson <c.christian.joensson@telia.com> writes:
> >
> > ChJ> I applied it to Hans et als. gc6.1alpha4 sources, it seems to
> > ChJ> work there.
> >
> > Great.
> >
> > ChJ> So Hans, what do we do now? Incorporate your patch into the gcc
> > ChJ> 3.1 branch and trunk? Test it first in gc6.1alpha5?
> >
> > As I understand it, you couldn't apply this patch to the GC currently
> > in the gcc tree, right? Could you modify the patch so it applies
> > (apply it by hand somehow) and then test that version of the GC?
> >
> > If that works, we will definitely check it in.
>
> I have used the attached patch (based on Hans' first suggested patch).
ehrm, here it is:
*** include/private/gcconfig.h.orig Tue Apr 16 19:08:52 2002
--- include/private/gcconfig.h Tue Apr 16 19:14:08 2002
***************
*** 820,830 ****
extern int _etext[];
# define DATAEND (_end)
# define SVR4
# ifdef __arch64__
- # define STACKBOTTOM ((ptr_t) 0x80000000000ULL)
# define DATASTART (ptr_t)GC_SysVGetDataStart(0x100000, _etext)
# else
- # define STACKBOTTOM ((ptr_t) 0xf0000000)
# define DATASTART (ptr_t)GC_SysVGetDataStart(0x10000, _etext)
# endif
# endif
--- 820,829 ----
extern int _etext[];
# define DATAEND (_end)
# define SVR4
+ # define LINUX_STACKBOTTOM
# ifdef __arch64__
# define DATASTART (ptr_t)GC_SysVGetDataStart(0x100000, _etext)
# else
# define DATASTART (ptr_t)GC_SysVGetDataStart(0x10000, _etext)
# endif
# endif
> The results are good (however, I happened to throw an an additional
> --enable-threads that I know cause troubles on sparc32/linux).
>
> I'd say the proposed patch works for sparc32, and I know Hans has
> a proposed patch for "all" sparc targets that I hope is in the process
> of being tested by folks having those arch available.
<snip>
Cheers,
/ChJ
next prev parent reply other threads:[~2002-04-17 7:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-17 10:19 Boehm, Hans
2002-04-17 10:54 ` Christian Jönsson
2002-04-17 13:00 ` 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=20020417072827.GA19253@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).