RFR(M): 8026251: New type profiling points: parameters to methods
roland.westrelin at oracle.com
Mon Oct 21 09:19:16 PDT 2013
> Yes, checking C1UpdateMethodData is a good thing to do for consistency. I don't think it needs to check C1ProfileCalls - that's to guard the receiver profiling code generation (perhaps not the best choice of option name). The original intention behind these flags was to turn off the new parts of profiling that were being added in C1 independently to debug problems more easily. If we want to follow the pattern, then we would need to add more C1ProfileX options. Otherwise the current code + C1UpdateMethodData checking is fine.
Thanks Igor. I added C1UpdateMethodData and left C1ProfileCalls out. TypeProfileLevel makes it possible to turn profiling on and off. I think it's good enough for debugging.
More information about the hotspot-compiler-dev