[jira] [Commented] (GROOVY-12023) create a PIC for indy

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on GROOVY-12023:
-----------------------------------------

sonarqubecloud[bot] commented on PR #2549:
URL: https://github.com/apache/groovy/pull/2549#issuecomment-4537509344

   ## [![Quality Gate 
Failed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadge/qg-failed-20px.png
 'Quality Gate 
Failed')](https://sonarcloud.io/dashboard?id=apache_groovy&pullRequest=2549) 
**Quality Gate failed**  
   Failed conditions  
   
![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/failed-16px.png
 '') [B Reliability Rating on New 
Code](https://sonarcloud.io/dashboard?id=apache_groovy&pullRequest=2549) 
(required ≥ A)  
     
   <!

> 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)