public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/33765] [4.3 regression] gcj internal compiler error when reading an empty file
Date: Sun, 28 Oct 2007 15:47:00 -0000	[thread overview]
Message-ID: <20071028154749.15699.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33765-5606@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from jakub at gcc dot gnu dot org  2007-10-28 15:47 -------
Created an attachment (id=14427)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14427&action=view)
gcc43-pr33765.patch

In this case (and e.g. also in case where you gcj -c package-info.java
from #297961) ecj1 creates an empty zip file, which contains just the
end central signature and nothing else (so doesn't have the usual
PK\3\4 magic, but PK\5\6).  The attached patch will handle it the same
as file with PK\3\4 magic, but it will still issue an error because the
expected
file wasn't found in the (empty) jar file.  Not sure what exact behavior we
want,
if giving an error is fine or if we e.g. should silently compile it into an
empty
.s file.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33765


  parent reply	other threads:[~2007-10-28 15:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-13 19:45 [Bug java/33765] New: " bero at arklinux dot org
2007-10-22  8:40 ` [Bug java/33765] " pinskia at gcc dot gnu dot org
2007-10-28 15:47 ` jakub at gcc dot gnu dot org [this message]
2007-10-30 14:28 ` jakub at gcc dot gnu dot org
2007-10-31 18:26 ` tromey at gcc dot gnu dot org
2007-10-31 18:36 ` bero at arklinux dot org
2007-10-31 23:42 ` jakub at gcc dot gnu dot org
2007-11-01 19:24 ` tromey at gcc dot gnu dot org
2007-11-02  8:02 ` jakub at gcc dot gnu dot org
2007-11-02 10:06 ` aph at gcc dot gnu dot org
2007-11-02 16:11 ` tromey at gcc dot gnu dot org
2007-11-02 20:02 ` tromey at gcc dot gnu dot org
2007-11-02 20:08 ` jakub at gcc dot gnu dot org

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=20071028154749.15699.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-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).