You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a crash happens in an AOT body, the jitdump should generate an AOT compilation. However, this is not as trivial as it might seem, as there are three scenarios:
I wonder about the value of [3] since typically we want to get to compilation logs.
Moreover, the advantage of jitdump is that it can generate a log from the the same JDK that produced the bad jitted body. If the AOT body has been produced in a previous run, we lose that advantage, so a compilation log from a brand new JVM invocation may be just as good.
Regarding 2, should the jitdump redo the AOT compilation, the AOT load, or both?
If a crash happens in an AOT body, the jitdump should generate an AOT compilation. However, this is not as trivial as it might seem, as there are three scenarios:
Regarding 2, should the jitdump redo the AOT compilation, the AOT load, or both?
Regarding 3, should the jitdump redo the AOT load?
The text was updated successfully, but these errors were encountered: