| Age | Commit message (Collapse) | Author |
|---|
|
* aosp/upstream-master:
Perform best-effort unescaping of command line options
Fix error reporting for resolution failures on nested annotations
Don't crash on type variables used as qualifiers in const exprs
Use a newer version of guava
Fix an NPE in constant expression binding of malformed annotations
Reformat with google-java-format
Miscellaneous cleanups
Report diagnostics for unterminated expressions at the beginning of the expression instead of at the end of the file, which is probably farther from the problem.
Fix error reporting for import resolution errors on nested types
Add flag control for the reduced classpath optimization
Bug: 122929601
Test: m checkbuild
Change-Id: I30c0efadd5379f668772bc047d54ccfbbce118f8
|
|
MOE_MIGRATED_REVID=226543883
|
|
Updates turbine to upstream 5a26f8cf360ab8f450d6268574a8a8ab50588d0d.
Test: m checkbuild
Change-Id: I611f1edd5c9a85cf06a23916410eb9b24cab811f
|
|
MOE_MIGRATED_REVID=219649528
|
|
in order to get equals and hashCode implementations.
MOE_MIGRATED_REVID=218399705
|
|
MOE_MIGRATED_REVID=218089802
|
|
|
|
|
|
|
|
MOE_MIGRATED_REVID=210113065
|
|
MOE_MIGRATED_REVID=207911913
|
|
Including handling module-info's in ct.sym for JDK 10 and up.
Don't assert on unsupported class file major versions; we'll
still find out if changes are necessary.
MOE_MIGRATED_REVID=207294946
|
|
This reverts upstream commit d0fcced7ecc9108d70ae2aea0ae3db00aacf3924.
We don't have checker framework in the tree, continue using jsr305.
Also convert one android.support.annotations.Nullable introduced
by db00737c711b291adf423c503284ce1dc01a13a6 to jsr305.
Test: m checkbuild
Change-Id: I3e4794368c1369ccb32f24e55df030afe6a784d7
|
|
MOE_MIGRATED_REVID=192318366
|
|
MOE_MIGRATED_REVID=177411000
|
|
MOE_MIGRATED_REVID=174583181
|
|
MOE_MIGRATED_REVID=165307508
|
|
|
|
|
|
MOE_MIGRATED_REVID=141337639
|
|
Instantiate types recursively; previously [T/e]A<T> worked but
[T/e]A<B<T>> didn't.
Also handle instantiating arrays with parametric element types, which
can't appear as top-level types during canonicalization but can appear
as type arguments (e.g. [T/e]A<T[]> -> A<e[]>).
The array instantiation case is interesting because it allows the
creation of arrays with wildcard element types. The JVMS signature
grammar [1] doesn't actually allow that, but both javac and ecj can be
coerced into emitting it:
class A<X> { class I {} }
class Test {
class B<Y> extends A<Y[]> {}
B<?>.I i; // LA<[*>.I;
}
To support this, restructure the type and signature models to make
wildcards first-class types, instead of only allowing them as top-level
type arguments.
[1] https://docs.oracle.com/javase/specs/jvms/se8/html/jvms-4.html#jvms-4.7.9.1
MOE_MIGRATED_REVID=137101539
|
|
and fix unnecessary casts.
MOE_MIGRATED_REVID=136857315
|
|
MOE_MIGRATED_REVID=136856567
|
|
in preparation for emitting jdeps.
MOE_MIGRATED_REVID=136757494
|
|
Constant field initializers, annotations, and a bunch of constant pool
entry kinds are absent, we won't need them for a bit.
MOE_MIGRATED_REVID=133635333
|
|
Handle classpaths: add them to the top-level type index, create bound
nodes backed by classfiles, and allow types on the classpath to be
resolved during binding.
MOE_MIGRATED_REVID=133328092
|
|
MOE_MIGRATED_REVID=133145316
|
|
MOE_MIGRATED_REVID=131095240
|
