RFR (S) 8027804: JCK resolveMethod test fails expecting AbstractMethodError

[harold seigel]

Hi Keith,

Thanks for the review.

Yes, it is a closed bug.  The bug involves a method in a subclass 
calling a default method in interface I when interface J implements I 
and contains an abstract method.  Instead of calling the default method, 
an AbstractMethodError should be throwin.

Thanks, Harold

On 11/26/2013 4:00 PM, Keith McGuigan wrote:
> Code looks good.  I can't access the JIRA record though -- "permission 
> denied".  Is it a 'closed' bug?
>
> --
> - Keith
>
>
> On Tue, Nov 26, 2013 at 2:19 PM, harold seigel 
> <harold.seigel at oracle.com <mailto:harold.seigel at oracle.com>> wrote:
>
>     Hi,
>
>     Please review this small change to fix bug 8027804.
>
>     In cases where the maximally specific method is abstract, the fix
>     creates an AbstractMethodError exception and message.  This
>     generates an overpass method.  The overpass method then gets added
>     to the default methods table where it can be found during method
>     resolution.
>
>     The fix was tested with the JCK lang and vm tests, the default
>     methods tests, ute vm.quick tests, and the jtreg hotspot, lang,
>     and util tests.
>
>     Open webrev: http://cr.openjdk.java.net/~hseigel/bug_8027804/
>     <http://cr.openjdk.java.net/%7Ehseigel/bug_8027804/>
>     <http://cr.openjdk.java.net/%7Ehseigel/bug_8027804/>
>
>     Bug: https://bugs.openjdk.java.net/browse/JDK-8027804
>
>     Thanks, Harold
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/attachments/20131126/3c4bb1af/attachment.html