RFR 8155674: Move javac towards a "by-file" compilation policy

Maurizio Cimadamore maurizio.cimadamore at oracle.com
Sun Dec 4 22:11:32 UTC 2016

Also don't forget that the cycle problem is temporary  - as discussed in 
that thread, the fix here is to actually get rid of erasure (which is 
something we did already in an experimental patch in Valhalla) which 
then removes the ordering problems with supertypes/subtypes. We plan to 
do further experiments with this in the Valhalla repo and move this code 
to 10 when ready.


On 02/12/16 02:18, Liam Miller-Cushon wrote:
> On Thu, Dec 1, 2016 at 6:06 PM, Jonathan Gibbons 
> <jonathan.gibbons at oracle.com <mailto:jonathan.gibbons at oracle.com>> wrote:
>     Does this address the potential problem with cycles that you
>     mentioned in
>     the original email?
> Not fully. It improves the current behaviour by ensuring files always 
> go through attr and flow as a unit, but classes may still be desugared 
> separately from their compilation unit.
> One of the test cases has compilation units [One, Two] and [Three, 
> Four], where Two extends Four, and Three extends One. There's no way 
> to linearize that so supertypes are desugared first and files are 
> desugared as a unit.
> Are there still plans to removethe ordering constraint in TransTypes?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/compiler-dev/attachments/20161204/c7d17145/attachment.html>

More information about the compiler-dev mailing list