public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: per@bothner.com
To: gcc-gnats@gcc.gnu.org
Subject: java/6425: jc1 generates fatal error on re-reading a class file
Date: Tue, 23 Apr 2002 08:46:00 -0000 [thread overview]
Message-ID: <20020423153933.23652.qmail@sources.redhat.com> (raw)
>Number: 6425
>Category: java
>Synopsis: jc1 generates fatal error on re-reading a class file
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-legal-code
>Submitter-Id: net
>Arrival-Date: Tue Apr 23 08:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Per Bothner
>Release: 3.1 20020421 (prerelease)
>Organization:
>Environment:
System: Linux eureka.bothner.com 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 unknown
Architecture: i686
<machine, os, target, libraries (multiple lines)>
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: /home/bothner/GNU/gcc3/configure --enable-threads --prefix=/home/bothner/GNU/install-gcc3 --enable-languages=C++,java
>Description:
A simple testcase causes jc1 to bail with the message
reading class gnu.math.RealNum for the second time from ./RealNum.class
This is a simplification of a problem ha prevents Kawa from working.
This is a regression from last time I tested gcj on Kawa.
>How-To-Repeat:
Uncompress the attached files.
cd to gnu/math.
Do 'make'
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/x-gzip; name="math-test.tgz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="math-test.tgz"
H4sIALN2xDwAA+2Y3WrbMBSAfVs9xblMYFZlx5IhZRddoaywjdHsBRRHdt04dvBPKYy+++TfpIHW
u4idNTvfjYgiyUZHn3TkIC4ujYFhzGGuy3XJmCtelw0Gcx1hMXdmccdglsWFbQAf+sVKiiyXKYCx
TPKHWKVvtuv7/4MS6PhvZP4w5CKo4s/ZX8XfruJvc8Yx/mPQxf82fFareyWj2yTVFfRRPskjPYNZ
jAnHeTP+tmjjL7glXN1ezFxmADvS89/lP4//VnprGSjQ64CW6+CKkG2xjEIPvEhmGRwsC/KbADQN
npJwBX5VPbmX+Y9iA3GxWar0EyzyNIyDL4XvqxSyZeFPdbeyK1S/qNxuVbyalOPqbjRPFp6M1Oou
ziftEBablvXVQJPp9Ep3fiEv5NTzdW50/uu5L0NxRO07+vxnrt3u/7Y10/WWwwX6Pwp9/tfLAtRz
roXNoPZc7wJo4nnQ+V9H9kT+zzr/BW/8d9D/MejzvznYO//rExs3gHNh53+Tiw2wAfT5b+3771T+
60QA/R+DXv874bu8X09YrosmM9jL3aG9Buj0PdQ/17usP1V5kcb6fhBFdSaP+8e/Qef/d7lWfhip
AZ5R+S/eu/877f3f5bZd+l9+BkT/R0DH3yzjT5N56zqtzCcXgfcIZgDmHaWXlJYlmN7hB4HqvAAz
gd1AhLwaaE4ubr5dLxY/r399/Uzn9WDV2DcA+6cOIV6kZKzbpxsw/b0RD97s1HOGIAiCIAiCIAiC
IAjykfgDgdqM+AAoAAA=
next reply other threads:[~2002-04-23 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 8:46 per [this message]
2002-04-24 18:09 tromey
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=20020423153933.23652.qmail@sources.redhat.com \
--to=per@bothner.com \
--cc=gcc-gnats@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).