On Mar 3, 2015, at 8:23 AM, Vladimir Ivanov <[email protected]>
wrote:
>
>> Suggestion: Instead of have the intrinsic expand to nothing, have it expand
>> to an uncommon trap (on the slow path), with the uncommon trap doing the
>> profile update operation (as currently coded).
> Right now, VM doesn't care about profiling logic at all. The intrinsic is
> used only to inject profile data and all profiling happens in Java code. Once
> MHI.profileBoolean is intrinsified (profile is injected), no profiling
> actions are performed.
What I'm thinking is that an uncommon trap could re-run the interpreter
definition of MHI.profileBoolean using Action_reinterpret.
That would update the state, wouldn't it? Then the compiler would recompile
(after a little time) and see the updated state.
— John
_______________________________________________
mlvm-dev mailing list
[email protected]
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
