RFR(XS): JDK-8114853 variable tracking size limit exceeded in vmStructs.cpp
Coleen Phillimore
coleen.phillimore at oracle.com
Thu Nov 19 15:33:34 UTC 2015
On 11/19/15 9:40 AM, Mikael Gerdin wrote:
> Hi,
>
> On 2015-11-19 12:58, Dmitry Samersoff wrote:
>> Everybody,
>>
>> Please review:
>>
>> http://cr.openjdk.java.net/~dsamersoff/JDK-8114853/webrev.01/
>
> Isn't it possible to set -fno-var-tracking-assignments for just
> vmstructs.cpp?
>
> In my opinion it's really helpful to have as much debug info as
> possible in the product binaries.
Or even turn off -g entirely for vmStructs? It's not really debuggable
anyway.
Coleen
>
> /Mikael
>
>
>>
>> Story:
>>
>> VTA fails on huge VMStructs::init() so this method is being compiled
>> twice.
>>
>> VTA[1] allows compiler to emit DWARF-3 debugging information for local
>> variable ever if this variable is optimized out at the cost of
>> compilation time and compiler memory consumption.
>>
>> So I decided to turn it off for entire hotspot build to reduce memory
>> footprint/increase compilation speed.
>>
>> 1. https://gcc.gnu.org/wiki/Var_Tracking_Assignments
>>
>> -Dmitry
>>
>
More information about the hotspot-runtime-dev
mailing list