-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Cleaning up write barrier code (#68124)
* Write barrier code cleanup 1) Delete leftovers from legacy codegen, including the "tgt" naming. 2) Do not second-guess the write barrier form when selecting a helper, always return "known" WBF from "gcIsWriteBarrierCandidate" instead. * Delete GTF_IND_TGT_ANYWHERE And create GTF_IND_TGT_HEAP instead, its logical opposite. For reference, the situation before this change was as follows: // Type of the ("simplified"/"base") address: // // - TYP_I_IMPL: checked write barrier // - TYP_REF: unchecked write barrier // - TYP_BYREF: // 1) No flags: unchecked write barrier // 2) TGT_ANYWHERE: checked write barrier The TYP_BYREF case will now look like this: // // 1) No flags: checked write barrier // 2) TGT_HEAP: unchecked write barrier The main benefit is that we get the default state (no flags) to be the conservatively correct one. * Add a quirk to avoid diffs on x86
- Loading branch information
1 parent
12c06c0
commit 10012c4
Showing
25 changed files
with
272 additions
and
356 deletions.
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
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
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
Oops, something went wrong.