[
https://issues.apache.org/jira/browse/GROOVY-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Sun updated GROOVY-8526:
-------------------------------
Description:
As [https://github.com/jacoco/jacoco/issues/626#issuecomment-349466549] shows:
"methods with unstructured locking aren't compiled and fall back to the
interpreter", which will impact performance.
We should check whether groovy contains similar issues in bytecode.
Java9+ is required and add JVM options to check: "-XX:+PrintCompilation
-Xlog:monitormismatch=info"
was:
As https://github.com/jacoco/jacoco/issues/626#issuecomment-349466549 shows:
"methods with unstructured locking aren't compiled and fall back to the
interpreter"
We should check whether groovy contains similar issues in bytecode.
Java9+ is required and add JVM options to check: "-XX:+PrintCompilation
-Xlog:monitormismatch=info"
> Check Unbalanced monitorenter / monitorexit instructions in bytecode
> --------------------------------------------------------------------
>
> Key: GROOVY-8526
> URL: https://issues.apache.org/jira/browse/GROOVY-8526
> Project: Groovy
> Issue Type: Task
> Components: bytecode
> Reporter: Daniel Sun
> Priority: Major
>
> As [https://github.com/jacoco/jacoco/issues/626#issuecomment-349466549] shows:
> "methods with unstructured locking aren't compiled and fall back to the
> interpreter", which will impact performance.
> We should check whether groovy contains similar issues in bytecode.
> Java9+ is required and add JVM options to check: "-XX:+PrintCompilation
> -Xlog:monitormismatch=info"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
