public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: davem@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/6383: boehm-gc busted on all sparc64 targets
Date: Sun, 21 Apr 2002 23:06:00 -0000	[thread overview]
Message-ID: <20020422060601.7627.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/6383; it has been noted by GNATS.

From: "David S. Miller" <davem@redhat.com>
To: jsturm@one-point.com
Cc: gcc-gnats@gcc.gnu.org, rth@redhat.com, tromey@redhat.com,
        gcc-bugs@gcc.gnu.org
Subject: Re: target/6383: boehm-gc busted on all sparc64 targets
Date: Sun, 21 Apr 2002 22:52:48 -0700 (PDT)

    From: Jeff Sturm <jsturm@one-point.com>
    Date: Mon, 22 Apr 2002 00:41:33 -0400 (EDT)
    
    Doh... DYNAMIC_LOADING isn't defined for sparc64-solaris.  There's part
    of your problem.  With the patch below I can run gctest.  I'll try some
    Java code once the build finishes.
    
    (This must've gotten reverted at the last gc import, I'm fairly certain
    it used to work.)
 
 If people don't mind I'm going to check in Jeff's fix for Solaris
 and a fix I have for the sparc64-linux-gnu boehm-gc failures so
 we can close this bug.
 
 Thanks for tracking this down and testing your fix Jeff.  I suspected
 that lack of DYNAMIC_LOADING for solaris sparc64 was bogus and I
 had noted it to tromey the other evening.


             reply	other threads:[~2002-04-22  6:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 23:06 David S. Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-22  8:46 Jeff Sturm
2002-04-21 23:12 davem
2002-04-21 21:46 Jeff Sturm
2002-04-21  4:00 davem
2002-04-19 21:40 davem
2002-04-19 21:16 davem

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=20020422060601.7627.qmail@sources.redhat.com \
    --to=davem@redhat.com \
    --cc=davem@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    /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).