Hi Dean,
to avoid escape analysis-eliminated allocations in the past @DontInline
has been sufficient. This means a simpler patch (no changes to native
code needed - added assertions notwithstanding) and passes your tests
with C2 (it'd concern me if Graal's EA sees through this trick, as it
might
Hi,
Could I have the update reviewed?
http://cr.openjdk.java.net/~xuelei/8215443/webrev.00/
The TransportContext.fatal() methods always throw exception. While the
compiler does not aware of it, and may not happy without following a
return statement. Currently, a lot never executable return
Just the complete the thread. Says "fatal() throws exception" is fine.
If this all only trying to make the compiler happy, you could just have
one "return null" at the bottom of the method. It is not necessary to
put a return after each fatal(). I will admit it could be less readable.
Or f
