clarification: Class file changes and pack200.

Alex Buckley alex.buckley at oracle.com
Mon Feb 11 11:55:11 PST 2013


Thanks Kumar.

For my part, I should have announced the changes to the MethodParameters 
attribute in a more visible way than using an existing thread [1].

Alex

[1] 
http://mail.openjdk.java.net/pipermail/enhanced-metadata-spec-discuss/2013-January/000134.html

On 2/11/2013 11:44 AM, Kumar Srinivasan wrote:
> Hello Eric, Alex,
>
> I have no objections to the proposed MethodParameters, my understanding
> at this time is that the MethodParameters may have more elements, that
> is fine
> from a pack200 perspective.
>
> Also the flag type is being changed from u4 to u2, I will need to adjust
> this on
> the pack200 spec. and the implementation as well, pack200 is very strongly
> typed.
>
> Since MP attr is generated via a flag, it does not cause any problems for
> pack200, however the pack200 tests do rely on
> com/sun/tools/javac/classfile.
>
> What this generally means to any  javac developer making changes to the
> back end,
> is that:
>    1. new class file spec. be submitted to ccc, and cc me on the
> submission, I have also
>        asked Joe to keep me in the loop if such changes come to ccc's
> attention.
>
>    2. run the pack200 regression tests in jdk/test/tools/pack200,
>        if there are failures, please file a bug and assign the bug to me.
>        Any failures left unfixed and/or disabled, can cause other issues
> to escape
>        into the JDK, spreading to other repositories, causing build
> failures.
>
> I hope this clarifies.
>
> Thanks
> Kumar
>
>
>
>
>
>
>



More information about the compiler-dev mailing list