[
https://issues.apache.org/jira/browse/GROOVY-12023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18083785#comment-18083785
] ASF GitHub Bot commented on GROOVY-12023: ----------------------------------------- sonarqubecloud[bot] commented on PR #2549: URL: https://github.com/apache/groovy/pull/2549#issuecomment-4553014005 ## [](https://sonarcloud.io/dashboard?id=apache_groovy&pullRequest=2549) **Quality Gate passed** Issues  [16 New issues](https://sonarcloud.io/project/issues?id=apache_groovy&pullRequest=2549&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true)  [0 Accepted issues](https://sonarcloud.io/project/issues?id=apache_groovy&pullRequest=2549&issueStatuses=ACCEPTED) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_groovy&pullRequest=2549&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true)  [84.7% Coverage on New Code](https://sonarcloud.io/component_measures?id=apache_groovy&pullRequest=2549&metric=new_coverage&view=list)  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_groovy&pullRequest=2549&metric=new_duplicated_lines_density&view=list) <! > create a PIC for indy > --------------------- > > Key: GROOVY-12023 > URL: https://issues.apache.org/jira/browse/GROOVY-12023 > Project: Groovy > Issue Type: Bug > Reporter: Jochen Theodorou > Assignee: Jochen Theodorou > Priority: Major > > What we currently have is essentially a two layer system in which we have the > target handle and cache for everything else. This can be seen as a PIC of > size 1 with a fallback cache for megamorphic cases. Here I propose to > implement a PIC of at least size 3 consisting of method handles where the > guard will use the next PIC element as fallback instead of going to the > cache. The goal is to reach a more stable configuration on the callsite for > JIT to optimize. -- This message was sent by Atlassian Jira (v8.20.10#820010)
