public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Christian Jönsson" <c.christian.joensson@telia.com>
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: Mon, 15 Apr 2002 23:08:00 -0000	[thread overview]
Message-ID: <20020416050226.GA13971@j-son.org> (raw)
In-Reply-To: <40700B4C02ABD5119F000090278766443BF1DD@hplex1.hpl.hp.com>

On Mon, Apr 15, 2002 at 07:58:54PM -0700, Boehm, Hans wrote:
> That stack pointer value doesn't look a lot like GC_stackbottom.  Just for
> grins, could you try the attached (completely untested) patch?  This makes
> linux/SPARC determine GC_stackbottom in the same way as on other Linux
> platforms, i.e. it first cheats and looks for a private glibc symbol, and
> reads the stack base from /proc if that fails.

This is a good idea to test I guess. But, the patch didn't apply
cleanly to my gcc-3.1 (Mon Apr 15 06:18:21 UTC 2002) sources.

***************
*** 815,825 ****
        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
--- 815,824 ----
        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


Hans, would you like me to update my gcc-3.1 source tree and patch
that and issue a rebuild or could you perhaps tell me what to do with
this particular case?

Cheers,

/ChJ

  reply	other threads:[~2002-04-16  5:02 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 [this message]
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
  -- 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=20020416050226.GA13971@j-son.org \
    --to=c.christian.joensson@telia.com \
    --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).