progress on method-gc / mangling questions

Mon Jan 28 15:22:00 GMT 2002

Adam Megacz wrote:
>Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:
>>>Java uses a subset of this. The mangling of function names is not likely 
>>to change, barring any bugs in our implementation. One special case is 
>>that int[] is mangled as JArray<int>.
>>>>Is that because a "java int[]" is really a "C++ JArray<int>", and not
>a "C++ int*"?
>
Right.
>>>- My binaries have a lot of sections named __Utf<n> where <n> is
>>> some number. What are these sections? String constants?
>>>>>>I don't know why they would be in different sections. The __Utf<n> 
>>symbols are Utf8Constants.
>>>>Even stranger, these are ".text" sections -- I thought .text was only
>for executable code, not for static data... If there is code in there,
>it makes sense that they're in seperate sections; I'm using
>-ffunction-sections.
>Odd. On linux they go into .rodata, or .rodata._Utf<n> when I use 
-ffunction-sections. Maybe its a win32 thing? Or it could be a bug with 
-ffunction-sections. Is the .s specifying ".text" explicitly for these 
constants?
regards
Bryce.