From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-80044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 12056 invoked by alias); 26 Dec 2003 13:43:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 12049 invoked by uid 48); 26 Dec 2003 13:43:49 -0000
Date: Fri, 26 Dec 2003 14:23:00 -0000
From: "guilhem at kaffe dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Message-ID: <20031226134345.13493.guilhem@kaffe.org>
Reply-To: gcc-bugzilla@gcc.gnu.org
Subject: [Bug java/13493] New: extra '<clinit>' generated in object file.
X-Bugzilla-Reason: CC
X-SW-Source: 2003-12/txt/msg02721.txt.bz2
List-Id: <gcc-bugs.sourceware.org>

a '<clinit>' is generated in the output file of gcc whereas it isn't present in
the class file. In that case it should not be enumerated as a declared method:
this can cause major troubles in the serialization logic of libjava which then
fails to produce a valid serialVersionUID. This seems to happen only in the
typical case of the following example:

public class C
{
        static class D extends C
        {
          private static final String s = "hello";
        }
}

If you try to compile this example, it will generate a static '<clinit>' method
in the inner class D, which should not happen as the class file doesn't have it.

-- 
           Summary: extra '<clinit>' generated in object file.
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: guilhem at kaffe dot org
                CC: gcc-bugs at gcc dot gnu dot org


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