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
This issue will track all the work for implementing field watch support in JITted methods (VM, compiler common code and codegens).
From @fjeremic:
"As things stand currently under full speed debug, when an agent requests a field to be watched we cannot JIT compile the method because we cannot respect the hooks for reporting accesses of the respective field. This limitation will be lifted by using the rdbar / rdbari opcodes to represent reads which have requested fields of certain types to be watched.
The JIT will generate read barriers for such fields of the correct type and the optimizer will treat them as normal loads. At codegen time we will reduce the read barrier to the load and insert a C helper call to notify the VM via a hook that a field has been read."
This issue will track all the work for implementing field watch support in JITted methods (VM, compiler common code and codegens).
From @fjeremic:
"As things stand currently under full speed debug, when an agent requests a field to be watched we cannot JIT compile the method because we cannot respect the hooks for reporting accesses of the respective field. This limitation will be lifted by using the rdbar / rdbari opcodes to represent reads which have requested fields of certain types to be watched.
The JIT will generate read barriers for such fields of the correct type and the optimizer will treat them as normal loads. At codegen time we will reduce the read barrier to the load and insert a C helper call to notify the VM via a hook that a field has been read."
So far, we have the following related issues:
@andrewcraik @fjeremic @cathyzhyi @DanHeidinga @gacholio
The text was updated successfully, but these errors were encountered: