public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5487: arm-linux-gcj cross-compiler generates bad assembler-code
Date: Mon, 25 Mar 2002 12:36:00 -0000 [thread overview]
Message-ID: <20020325203601.10224.qmail@sources.redhat.com> (raw)
The following reply was made to PR java/5487; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/5487: arm-linux-gcj cross-compiler generates bad assembler-code
Date: 25 Mar 2002 14:04:48 -0700
>>>>> "Richard" == Richard Earnshaw <rearnsha@arm.com> writes:
Richard> What we do not want
Richard> ...
Richard> The location (URL) of the package that failed to build (we won't
Richard> download it, anyway, since you've already given us what we need to
Richard> duplicate the bug, haven't you? :-)
Yeah. Java is a little different from C or C++. You can't send a
`.i' file that encapsulates everything you need for the bug. Still, I
agree that downloading something is a pain and it is much, much more
convenient to have a small archive that demonstrates the bug.
OTOH, rhug is sort of a special case. It is one of the important gcj
applications that we want to build out of the box.
Tom
next reply other threads:[~2002-03-25 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 12:36 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-01 18:26 neroden
2002-03-26 5:46 Richard Earnshaw
2002-03-25 3:46 Richard Earnshaw
2002-03-23 19:36 Tom Tromey
2002-03-23 9:47 rearnsha
2002-01-25 1:46 jsantala
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=20020325203601.10224.qmail@sources.redhat.com \
--to=tromey@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).