-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extending the current wrtbar opcode to xwrtbar/xwrtbari #2948
Comments
5 tasks
cathyzhyi
pushed a commit
to cathyzhyi/omr
that referenced
this issue
Oct 4, 2018
The xwrtbar/xwrtbari opcodes are added to represent both the store as well as its side effects like checking object address against tenure address range for GC, notifying the VM of the store or other similar activities. This PR adds the most basic supports for write barrier opcodes. The exist wrtbar/wrtbari are change to awrtbar/awrtbari for consistency. By default write barriers use store handlers and evaluators. issue: eclipse-omr#2948 Signed-off-by: Yi Zhang <[email protected]>
cathyzhyi
pushed a commit
to cathyzhyi/omr
that referenced
this issue
Oct 4, 2018
The xwrtbar/xwrtbari opcodes are added to represent both the store as well as its side effects like checking object address against tenure address range for GC, notifying the VM of the store or other similar activities. This PR adds the most basic supports for write barrier opcodes. The exist wrtbar/wrtbari are change to awrtbar/awrtbari for consistency. By default write barriers use store handlers and evaluators. issue: eclipse-omr#2948 Signed-off-by: Yi Zhang <[email protected]>
cathyzhyi
pushed a commit
to cathyzhyi/omr
that referenced
this issue
Oct 4, 2018
The xwrtbar/xwrtbari opcodes are added to represent both the store as well as its side effects like checking object address against tenure address range for GC, notifying the VM of the store or other similar activities. This PR adds the most basic supports for write barrier opcodes. The exist wrtbar/wrtbari are change to awrtbar/awrtbari for consistency. By default write barriers use store handlers and evaluators. issue: eclipse-omr#2948 Signed-off-by: Yi Zhang <[email protected]>
cathyzhyi
pushed a commit
to cathyzhyi/omr
that referenced
this issue
Oct 4, 2018
The xwrtbar/xwrtbari opcodes are added to represent both the store as well as its side effects like checking object address against tenure address range for GC, notifying the VM of the store or other similar activities. This PR adds the most basic supports for write barrier opcodes. The exist wrtbar/wrtbari are change to awrtbar/awrtbari for consistency. By default write barriers use store handlers and evaluators. issue: eclipse-omr#2948 Signed-off-by: Yi Zhang <[email protected]>
cathyzhyi
pushed a commit
to cathyzhyi/omr
that referenced
this issue
Oct 4, 2018
The xwrtbar/xwrtbari opcodes are added to represent both the store as well as its side effects like checking object address against tenure address range for GC, notifying the VM of the store or other similar activities. This PR adds the most basic supports for write barrier opcodes. The exist wrtbar/wrtbari are change to awrtbar/awrtbari for consistency. By default write barriers use store handlers and evaluators. issue: eclipse-omr#2948 Signed-off-by: Yi Zhang <[email protected]>
cathyzhyi
pushed a commit
to cathyzhyi/omr
that referenced
this issue
Oct 5, 2018
The xwrtbar/xwrtbari opcodes are added to represent both the store as well as its side effects like checking object address against tenure address range for GC, notifying the VM of the store or other similar activities. This PR adds the most basic supports for write barrier opcodes. The exist wrtbar/wrtbari are change to awrtbar/awrtbari for consistency. By default write barriers use store handlers and evaluators. issue: eclipse-omr#2948 Signed-off-by: Yi Zhang <[email protected]>
cathyzhyi
pushed a commit
to cathyzhyi/omr
that referenced
this issue
Oct 9, 2018
The xwrtbar/xwrtbari opcodes are added to represent both the store as well as its side effects like checking object address against tenure address range for GC, notifying the VM of the store or other similar activities. This PR adds the most basic supports for write barrier opcodes. The exist wrtbar/wrtbari are change to awrtbar/awrtbari for consistency. By default write barriers use store handlers and evaluators. issue: eclipse-omr#2948 Signed-off-by: Yi Zhang <[email protected]>
cathyzhyi
pushed a commit
to cathyzhyi/omr
that referenced
this issue
Oct 24, 2018
The xwrtbar/xwrtbari opcodes are added to represent both the store as well as its side effects like checking object address against tenure address range for GC, notifying the VM of the store or other similar activities. This PR adds the most basic supports for write barrier opcodes. The exist wrtbar/wrtbari are change to awrtbar/awrtbari for consistency. By default write barriers use store handlers and evaluators. issue: eclipse-omr#2948 Signed-off-by: Yi Zhang <[email protected]>
related work has been completed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Write barrier opcodes are needed to represent a store as well as the extra side effects like notify the VM of the write for debugging purpose. There are current already
wrtbar
andwrtbari
for address type direct and indirect stores and we are extending the opcodes and the syntax to other types.Indirect write barrier looks like the following:
Direct write barrier looks like the following:
see PR #3027 for actual implementation
The text was updated successfully, but these errors were encountered: