-
Enhancement
-
Resolution: Fixed
-
P4
-
hs12
-
b02
-
sparc
-
solaris_10
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2174828 | 6u14 | Vladimir Kozlov | P3 | Resolved | Fixed | b01 |
JDK-2172207 | 6u5p | Vladimir Kozlov | P3 | Resolved | Fixed | b01 |
jvm2008 'serial' benchmark has code which calls String.equals(str1, str2)
for 2 strings produced by StringBuilder.toString(). The first check in String.equals()
could be optimized out since during the compilation due to inlining we know that
it compares 2 newly allocated strings.
for 2 strings produced by StringBuilder.toString(). The first check in String.equals()
could be optimized out since during the compilation due to inlining we know that
it compares 2 newly allocated strings.
- backported by
-
JDK-2172207 Optimize CmpP for allocations
- Resolved
-
JDK-2174828 Optimize CmpP for allocations
- Resolved
- relates to
-
JDK-6692301 Side effect in NumberFormat tests with -server -Xcomp (all platforms, 6u5 perf release b01)
- Resolved
-
JDK-6686791 Side effect in NumberFormat tests with -server -Xcomp (all platforms, 6u5 perf release b01)
- Closed