TraceTypeProfile as diagnostic option (original) (raw)
Aleksey Shipilev aleksey.shipilev at oracle.com
Mon Sep 10 10:44:51 PDT 2012
- Previous message: TraceTypeProfile as diagnostic option
- Next message: TraceTypeProfile as diagnostic option
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 09/10/2012 09:22 PM, Vladimir Kozlov wrote:
We need to be careful here. It will increase product VM size (currently that code is under #ifndef PRODUCT) and embedded group will kill us for that. I think we should look on this case by case. You still can figure out that it is bimorphic call since they have the same bci (@ 4).
What is the reasonable increase in VM size we (they) could tolerate? I can make the prototype change and figure out the actual increase. Looks like there is a single small printing subroutine and two calls.
-Aleksey.
- Previous message: TraceTypeProfile as diagnostic option
- Next message: TraceTypeProfile as diagnostic option
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the hotspot-compiler-dev mailing list