Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Always generate write_barrier for VTABLE.
Reason for it next: 1. Aggregate PMC in Gen0. 2. We invoke write_barrier(PMC). Which is ignored. 3. VTABLE_foo() allocate new PMC. 4. Aggregate PMC moved into Gen1. 5. Content of PMC gets updated without triggering write barrier. To avoid it we store result of original VTABLE and invoke write_barrier after.
- Loading branch information
Showing
3 changed files
with
50 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters