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 16:16:00 -0000 [thread overview] Message-ID: <20020424231602.9036.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: tromey@redhat.com Cc: davem@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, ghazi@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 19:12:57 -0400 (EDT) > From: Tom Tromey <tromey@redhat.com> > > >>>>> "Kaveh" == Kaveh R Ghazi <ghazi@caip.rutgers.edu> writes: > > Kaveh> I'm not sure what problem you are seeing or why. Can you > Kaveh> provide more detail? Perhaps it makes sense to open a separate > Kaveh> PR. > > I am seeing the same behavior I saw before the patch went in. > The GC crashes in the same way. > At this point I'm assuming there is just something wrong with my build. > I'm not very concerned about it, and anyway I don't have the time to > look into it. > Tom Tom - Here's an independent example that leads me to believe its truly fixed. A 4/18 build on a sparcv9 target had 257 failures, whereas a 4/22 build had only 4 failures. See: http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg00685.html http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg00820.html So I also suspect there's something wrong in your personal build. But it could also be something subtly different about your box like the kernel version, etc. I can't say for sure. --Kaveh -- Kaveh R. Ghazi Director of Systems Architecture ghazi@caip.rutgers.edu Qwest Global Services
next reply other threads:[~2002-04-24 23:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-24 16:16 Kaveh R. Ghazi [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-24 16:06 Tom Tromey 2002-04-24 13:06 Kaveh R. Ghazi 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=20020424231602.9036.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).