public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> 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: <20020424200603.543.qmail@sources.redhat.com> (raw) The following reply was made to PR libgcj/6092; it has been noted by GNATS. From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> To: ghazi@gcc.gnu.org, tromey@redhat.com Cc: davem@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-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 16:05:47 -0400 (EDT) > From: Tom Tromey <tromey@redhat.com> > > 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) > Tom The "make check" works for me in both the regular (m32) and sparcv9 (m64) directories (output listed below.) I'm not sure what problem you are seeing or why. Can you provide more detail? Perhaps it makes sense to open a separate PR. in boehm-gc: > Completed 3 tests > Allocated 5252866 collectable objects > Allocated 306 uncollectable objects > Allocated 3476354 atomic objects > Allocated 32854 stubborn objects > Finalized 6622/6622 objects - finalization is probably ok > Total number of bytes allocated is 185271172 > Final heap size is 13213696 bytes > Collector appears to work > Completed 87 collections > PASS: gctest > ================== > All 1 tests passed > ================== > make[2]: Leaving directory > `/teal/caip5/ghazi/gcc-testing/branch/build/sparc-sun-solaris2.7/boehm-gc' in sparcv9/boehm-gc: > Completed 3 tests > Allocated 5124806 collectable objects > Allocated 306 uncollectable objects > Allocated 3094311 atomic objects > Allocated 32895 stubborn objects > Finalized 6675/6675 objects - finalization is probably ok > Total number of bytes allocated is 230972168 > Final heap size is 23150592 bytes > Collector appears to work > Completed 63 collections > PASS: gctest > ================== > All 1 tests passed > ================== > make[2]: Leaving directory > `/teal/caip5/ghazi/gcc-testing/branch/build/sparc-sun-solaris2.7/sparcv9/boehm-gc' -- Kaveh R. Ghazi Director of Systems Architecture ghazi@caip.rutgers.edu Qwest Global Services
next 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 Kaveh R. Ghazi [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 David S. Miller 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=20020424200603.543.qmail@sources.redhat.com \ --to=ghazi@caip.rutgers.edu \ --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: linkBe 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).