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: libgcj/6092: sparc-sun-solaris2.7 gcc-3.1 has hundreds of libjava failures with -m64
Date: Wed, 24 Apr 2002 13:06:00 -0000	[thread overview]
Message-ID: <20020424200601.516.qmail@sources.redhat.com> (raw)

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

From: "David S. Miller" <davem@redhat.com>
To: tromey@redhat.com
Cc: ghazi@gcc.gnu.org, davem@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
        gcc-prs@gcc.gnu.org, ghazi@caip.rutgers.edu, java-prs@gcc.gnu.org,
        gcc-gnats@gcc.gnu.org
Subject: Re: libgcj/6092: sparc-sun-solaris2.7 gcc-3.1 has hundreds of
 libjava failures with -m64
Date: Wed, 24 Apr 2002 12:49:13 -0700 (PDT)

    From: Tom Tromey <tromey@redhat.com>
    Date: 24 Apr 2002 13:58:23 -0600
 
    Kaveh> See -m64 java results here:
    Kaveh> http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg00875.html
        
    I can't argue with those results.
    I do wonder why my Solaris 2.7 build still fails.
    Do the GC tests work for you?
    (`make check' in the boehm-gc target build directory)
 
 With that small number of failures, boehm-gc is working.
 If it isn't working you get at least 140 failures.


             reply	other threads:[~2002-04-24 20:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24 13:06 David S. Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-24 16:16 Kaveh R. Ghazi
2002-04-24 16:06 Tom Tromey
2002-04-24 13:06 Kaveh R. Ghazi
2002-04-24 12:56 Tom Tromey
2002-04-24 12:41 ghazi
2002-04-19 18:36 Tom Tromey
2002-04-19 15:56 Tom Tromey
2002-04-19 11:54 rth

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=20020424200601.516.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).