RFR(XS): JDK-8114853 variable tracking size limit exceeded in vmStructs.cpp (original) (raw)
Mikael Gerdin mikael.gerdin at oracle.com
Thu Dec 3 15:39:27 UTC 2015
- Previous message (by thread): RFR(XS): JDK-8114853 variable tracking size limit exceeded in vmStructs.cpp
- Next message (by thread): RFR(XS): JDK-8114853 variable tracking size limit exceeded in vmStructs.cpp
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Dmitry,
On 2015-12-03 14:53, Dmitry Samersoff wrote:
Everybody,
I'd followed common opinion and turn off tracking of variable assignment for vmStructs file only. Updated webrev is here: http://cr.openjdk.java.net/~dsamersoff/JDK-8114853/webrev.02/
Looks good to me. /Mikael
-Dmitry On 2015-11-19 14:58, Dmitry Samersoff wrote: Everybody,
Please review: http://cr.openjdk.java.net/~dsamersoff/JDK-8114853/webrev.01/ 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/VarTrackingAssignments -Dmitry
- Previous message (by thread): RFR(XS): JDK-8114853 variable tracking size limit exceeded in vmStructs.cpp
- Next message (by thread): RFR(XS): JDK-8114853 variable tracking size limit exceeded in vmStructs.cpp
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]