Hi,
On Thu, 2015-12-03 at 16:53 +0300, 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. Thanks
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
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/
-Dmitry
On 2015-11-19 14:58, Dmitry Samersoff wrote:
> Everybody,
>
> Please review:
>
> http://c
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 t
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