-
Enhancement
-
Resolution: Not an Issue
-
P4
-
10
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8195786 | 11 | Eric Caspole | P4 | Resolved | Fixed | b01 |
The compilation log has information about intrinsics but the LogCompilation tool doesn't read it now. For example, +PrintIntrinsics would show
@ 31 java.lang.String::isLatin1 (19 bytes) inline (hot)
@ 45 java.lang.StringLatin1::equals (36 bytes) (intrinsic)
but LogCompilation shows:
@ 31 java.lang.String::isLatin1 succeed: inline (hot) (end time: 0.4590 nodes: 205 live: 196)
@ 45 java.lang.StringLatin1::equals (36 bytes) (end time: 0.0000)
@ 31 java.lang.String::isLatin1 (19 bytes) inline (hot)
@ 45 java.lang.StringLatin1::equals (36 bytes) (intrinsic)
but LogCompilation shows:
@ 31 java.lang.String::isLatin1 succeed: inline (hot) (end time: 0.4590 nodes: 205 live: 196)
@ 45 java.lang.StringLatin1::equals (36 bytes) (end time: 0.0000)
- backport of
-
JDK-8194768 LogCompilation could show the intrinsics more like +PrintIntrinsics
-
- Closed
-
- backported by
-
-
- Resolved
-