For incremental barriers we check if compartment()->needsBarrier to defer the cost when we are not in a GC cycle. We cannot do this for cross-generation barriers. We need to remove the checks on the post barriers and rename the enum to something more specific.
Created attachment 582152 [details] [diff] [review] v1: more post barriers on base The changes to flatten are straightforward. I do not think we need pre barriers on init, but do let me know if I am mistaken here.
Attachment #582152 - Flags: review?(wmccloskey)
Attachment #582152 - Flags: review?(wmccloskey) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla11
You need to log in before you can comment on or make changes to this bug.