[ 
https://issues.apache.org/jira/browse/LANG-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruslan Cheremin updated LANG-1262:
----------------------------------
    Description: 
Issue is the same as in LANG-1218: 
CompareToBuilder.append(Object,Object,Comparator) is quite big, due to in-place 
arrays processing, and thus breaching inlining threshold (325 bytecodes):
```
o.a.c.l.b.CompareToBuilder::append (346 bytes)   hot method too big
```
This prevents CompareToBuilder object itself from being scalarized.

Fix may be the same, as in LANG-1218: extract arrays processing into separate 
method.

  was:
Issue is the same as in https://issues.apache.org/jira/browse/LANG-1218: 
CompareToBuilder.append(Object,Object,Comparator) is quite big, due to in-place 
arrays processing, and thus breaching inlining threshold (325 bytecodes):
```
o.a.c.l.b.CompareToBuilder::append (346 bytes)   hot method too big
```
This prevents CompareToBuilder object itself from being scalarized.

Fix may be the same, as in LANG-1218: extract arrays processing into separate 
method.


> CompareToBuilder.append(Object,Object,Comparator) method is too big to be 
> inlined
> ---------------------------------------------------------------------------------
>
>                 Key: LANG-1262
>                 URL: https://issues.apache.org/jira/browse/LANG-1262
>             Project: Commons Lang
>          Issue Type: Bug
>          Components: lang.builder.*
>    Affects Versions: 3.4
>            Reporter: Ruslan Cheremin
>
> Issue is the same as in LANG-1218: 
> CompareToBuilder.append(Object,Object,Comparator) is quite big, due to 
> in-place arrays processing, and thus breaching inlining threshold (325 
> bytecodes):
> ```
> o.a.c.l.b.CompareToBuilder::append (346 bytes)   hot method too big
> ```
> This prevents CompareToBuilder object itself from being scalarized.
> Fix may be the same, as in LANG-1218: extract arrays processing into separate 
> method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to