RFR(XS): 8144852: Corrupted oop in nmethod

John Rose john.r.rose at oracle.com
Wed Jan 6 17:32:54 UTC 2016

On Dec 16, 2015, at 3:38 PM, Ioi Lam <ioi.lam at oracle.com> wrote:
> Adding non_oop_word to oopDesc::print_*_on would imply that it's OK to assign this value in a more general context, which is not true.

So put in a comment.  The print_on stuff is for us to use in debuggers and tracing code, not for end users who might be confused.

> So I would suggest keeping knowledge of non_oop_word inside nmethod for now, and we can revisit this if other places start to use non_oop_word.

Either way is OK with me.  But I like my print functions to be as forgiving as possible; don't you?

— John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20160106/0e94d684/attachment-0001.html>

More information about the hotspot-compiler-dev mailing list