This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Problem with renamed static constants in .o file

From: Bryce McKinlay <mckinlay at redhat dot com>
To: Andrew Haley <aph at redhat dot com>
Cc: Dave Menendez <dave at sycamorehq dot com>, java at gcc dot gnu dot org
Date: Tue, 28 Sep 2004 14:59:55 -0400
Subject: Re: Problem with renamed static constants in .o file
References: <1096393919.2353.59.camel@localhost.localdomain> <16729.42457.944299.277886@cuddles.cambridge.redhat.com> <1096395688.2353.66.camel@localhost.localdomain> <16729.44049.485256.991998@cuddles.cambridge.redhat.com>

Andrew Haley wrote:

Dave Menendez writes: > On Tue, 2004-09-28 at 13:56, Andrew Haley wrote: > > What does the asm output of "gcj -S" look like? > > > > Andrew. > > Here's an excerpt. The only correct item I see is the "ascii" property > a few lines in.

Yeah. I think that this is a divergence between the way that Java and C++ names are mangled.

I believe "__U" is used by GCJ as a prefix to encode unicode characters as the assembler may only support ASCII. If the string "__U" actually appears in an indentifier, it is encoded as "__U_". In this case it looks like a bug in GCJs name mangling because its also encoding "_U" in this way, which shouldn't be neccessary.

In any case, the mangled name should be reflected in the header that gcjh generates, so theres another bug there.

Bryce

References:
- Problem with renamed static constants in .o file
  - From: Dave Menendez
- Problem with renamed static constants in .o file
  - From: Andrew Haley
- Problem with renamed static constants in .o file
  - From: Dave Menendez
- Problem with renamed static constants in .o file
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]