public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@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: Fri, 19 Apr 2002 15:56:00 -0000 [thread overview]
Message-ID: <20020419225602.5730.qmail@sources.redhat.com> (raw)
The following reply was made to PR libgcj/6092; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: rth@gcc.gnu.org
Cc: davem@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
ghazi@caip.rutgers.edu, java-prs@gcc.gnu.org, nobody@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: 19 Apr 2002 16:59:21 -0600
>>>>> "rth" == rth <rth@gcc.gnu.org> writes:
rth> Dave sez libffi for sparc64 is borked.
This is a GC problem, not a libffi problem. The boehm-gc gctest
program crashes in the same way as every java program; also a libffi
problem wouldn't show itself as a systematic failure of all the
libjava execute tests (most programs never use libffi).
rth> I disbelieve this is a regression, so I've downgraded
rth> priority to medium.
I don't think it is a regression either. However, that leaves us in
the odd situation where we build a compiler where the -m32 libraries
work and the -m64 ones do not. This is why I had left it as high
priority. That said, it isn't clear I'll actually be able to finish
debugging this before the deadline, either.
Tom
next reply other threads:[~2002-04-19 22:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 15:56 Tom Tromey [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 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 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=20020419225602.5730.qmail@sources.redhat.com \
--to=tromey@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).