public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "timo dot lindfors at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/20088] New: -findirect-dispatch: error: final field 'text' may not have been initialized
Date: Sat, 19 Feb 2005 20:11:00 -0000	[thread overview]
Message-ID: <20050219193616.20088.timo.lindfors@iki.fi> (raw)

Compiling

public class FinalTest2 {
        public static final String text = "foo";
        public static void main(String[] args) {
                System.out.println(text);
        }

}

fails if I use -findirect-dispatch:

$ gcj -findirect-dispatch FinalTest2.java --main=FinalTest2 -o FinalTest2
FinalTest2.java: In class 'FinalTest2':
FinalTest2.java: In method '<clinit>()':
FinalTest2.java:2: error: final field 'text' may not have been initialized
FinalTest2.java: At top level:
FinalTest2.java:1: 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: -findirect-dispatch: error: final field 'text' may not
                    have been initialized
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: timo dot lindfors at iki dot fi
                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=20088


             reply	other threads:[~2005-02-19 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-19 20:11 timo dot lindfors at iki dot fi [this message]
2005-02-20 15:07 ` [Bug java/20088] " pinskia at gcc dot gnu dot org
2005-05-17 14:51 ` aph at gcc dot gnu dot org
2005-05-17 14:56 ` aph at gcc dot gnu dot org
2005-05-17 14:56 ` 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=20050219193616.20088.timo.lindfors@iki.fi \
    --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).