[jira] [Commented] (GROOVY-9126) Unreachable line numbers after ARETURN in bytecode

["Roger Diller (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GROOVY-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020709#comment-17020709 ] 

Roger Diller commented on GROOVY-9126:
--------------------------------------

Some information.... if I use Groovy 2.5.8 I get a 10.84% drop in code coverage on my project. With the new 2.5.9 release, I get a 1.80% drop.

*Conclusion*: It improved dramatically but I am still losing a bit of code coverage. It's not a big deal to me, but I just wanted to provide this info for awareness. If I can provide any more specific details, please do ask!

> Unreachable line numbers after ARETURN in bytecode
> --------------------------------------------------
>
>                 Key: GROOVY-9126
>                 URL: https://issues.apache.org/jira/browse/GROOVY-9126
>             Project: Groovy
>          Issue Type: Bug
>          Components: bytecode
>    Affects Versions: 2.5.5, 2.5.6, 2.5.7
>            Reporter: Adam Estabrook
>            Assignee: Daniel Sun
>            Priority: Major
>             Fix For: 2.5.9, 3.0.0-rc-2
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Starting with Groovy 2.5.5, unreachable line numbers were added to the byte code. This causes tools like JaCoCo to report uncovered lines. Removing these line numbers after the ARETURN would be helpful.
> [https://github.com/jacoco/jacoco/issues/884]
> ARETURN
>  L1
>  LINENUMBER 16 L1 <-- new line number that cant be hit after ARETURN
>  FRAME FULL [] [java/lang/Throwable]
>  NOP
>  ATHROW
>  LOCALVARIABLE this Lcom/company/Form; L0 L1 0
>  MAXSTACK = 2
>  MAXLOCALS = 1
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)