Age | Commit message (Collapse) | Author |
|
Change-Id: Ia40baedd800ead09fa46d305200843e4e32481fc
|
|
Change-Id: Ibed2f8da1eeb903c159b28ae9a3ab8f969858b40
|
|
jdk8u242 update
|
|
|
|
Reviewed-by: andrew
|
|
Summary: bitset for alive variables contains info about variables out of range
Reviewed-by: mcimadamore
Contributed-by: srikanth.adayapalam@oracle.com
|
|
jdk8u232-ga
|
|
|
|
Reviewed-by: jjg, rhalade, skoivu
|
|
Summary: Updated the info based on MUSCLE v1.8.24
Reviewed-by: ascarpino
|
|
Reviewed-by: prr, jdv, kcr
|
|
Reviewed-by: adinn, shade, andrew
|
|
Reviewed-by: jjg
|
|
Original JDK issue: https://bugs.openjdk.java.net/browse/JDK-8224161
Fix in JDK: http://hg.openjdk.java.net/jdk/jdk/rev/28f4594b19c2
Related IJI issue: https://youtrack.jetbrains.com/issue/IJI-167
|
|
Update 8u222
|
|
|
|
Change-Id: I9da87d83909a618b050e336e51b5aa4fff6eff1c
|
|
Reviewed-by: lancea, clanger, andrew
|
|
Reviewed-by: serb, dmarkov, andrew
|
|
Reviewed-by: prr
|
|
Reviewed-by: clanger
|
|
provided
Summary: Handle exceptions thrown while loading annotation processors.
Reviewed-by: jlahoda, andrew
|
|
Reviewed-by: phh
|
|
OpenJDK BUG: https://bugs.openjdk.java.net/browse/JDK-8177486
Cherry pick from OpenJDK: b2f2bdba0472
|
|
jdk-8u212 update
|
|
|
|
Reviewed-by: serb, erikj
|
|
When reading methods, make sure to invalidate read parameter
annotations and names between reading methods, even if saveParameterNames
is not set. Because there is validation that length of runtime in/visible
annotations is the same as the number of parameters, previously we could
run into issues.
Related to https://bugs.openjdk.java.net/browse/JDK-8177486
|
|
In aosp/Idcca9709603a58da5f067ca32abe1b9f5dc45496 we switched
to always loading all parameter names. However, this may cause issues
when e.g. class <init> method is suppose to contain synthetic parameters
but it does not. ClassReader will try to skip the synthetic params, but
because they do not exist, NPE will occur.
We work around this issue by restoring the previous behavior, which
was to retrieve the param names only when saveParameterNames is true.
There is one drawback though. Previously, if saveParameterNames was false,
we would get invalid names (arg0, arg1...), but annotations would be
correct. With this change, we will get invalid names without any
annotations. However, annotation processing which is the primary user
of these APIs always sets saveParameterNames to true, so there should
not be any issues.
Related to https://bugs.openjdk.java.net/browse/JDK-8177486
|
|
parameters have annotations
8177486: Incorrect handling of mandated parameter names in MethodParameters attributes
cherry-pick from openjdk: 89f6aa26fd6c
Change-Id: Idcca9709603a58da5f067ca32abe1b9f5dc45496
|
|
Change-Id: I3b87c8fd9cfb7332d4bb123b326076e863e5c7c1
|
|
|
|
|
|
Reviewed-by: prr
|
|
Reviewed-by: coffeys
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reviewed-by: prr
|
|
|
|
|
|
|
|
|
|
|
|
|