tree 0f10bf1c45f5a9f6b0f00181f282f19248a7817d
parent b44553224c3a9ff38c32e34c583a114a5a7f8b50
author Nicolas Geoffray <ngeoffray@google.com> 1482225942 +0000
committer Nicolas Geoffray <ngeoffray@google.com> 1482333738 +0000

Support non-exact upper bound of HBoundType.

It used to not affect the analysis, but in order to recognize:
if (foo.getClass() == Foo.class)

We now need to differentiate between an exact and a non-exact
upper bound. Until now the "exact" flag on upper bounds was
there for convenience:
1) re-use of the same data structure
2) we mostly cared about HLoadClass as upper bounds.

Test: test-art-host
Test: master build with prebuilts
Test: apk scanner
Change-Id: I3a1f5e4d489a715a4545becee4c8c80f7d152fc0