public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "ovidr at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/18945] New: gcj ICE with -findirect-dispatch
Date: Sun, 12 Dec 2004 18:33:00 -0000	[thread overview]
Message-ID: <20041212183348.18945.ovidr@users.sourceforge.net> (raw)

gcc version 4.0.0 20041130 (experimental)

gcj -c -findirect-dispatch Base64InputStream.java

Base64InputStream.java: In class 'gnu.crypto.pki.io.Base64InputStream':
Base64InputStream.java: In method '<clinit>()':
Base64InputStream.java:59: error: final field 'BASE_64' may not have been
initialized
Base64InputStream.java: At top level:
Base64InputStream.java:52: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

-- 
           Summary: gcj ICE with -findirect-dispatch
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ovidr at users dot sourceforge dot net
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


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


             reply	other threads:[~2004-12-12 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-12 18:33 ovidr at users dot sourceforge dot net [this message]
2004-12-12 18:34 ` [Bug java/18945] " ovidr at users dot sourceforge dot net
2004-12-13 21:40 ` tromey at gcc dot gnu dot org
2005-01-15  6:07 ` pinskia at gcc dot gnu dot org
2005-05-17 14:52 ` aph 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=20041212183348.18945.ovidr@users.sourceforge.net \
    --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).