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

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

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

   ## ✅ All tests passed ✅
   
   🏷️ Commit: da154cf773eeaef55a10cb6c644fa135e833b661
   ▶️ Tests:  199408 executed
   ⚪️ Checks: 56/56 completed
   
   ---
   _Learn more about TestLens at [testlens.app](https://testlens.app)._
   




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

Reply via email to