The default bug view has changed. See this FAQ.

Add JSGC_GENERATIONAL flag to build system

RESOLVED FIXED in mozilla13

Status

()

Core
JavaScript Engine
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: terrence, Assigned: terrence)

Tracking

Trunk
mozilla13
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

5 years ago
These are already in the tree in several places to protect (empty) post write barriers.  We should get these methods tested on more compilers by exposing them while they are still empty.
(Assignee)

Comment 1

5 years ago
Created attachment 586617 [details] [diff] [review]
v1: trivial

This is copied directly from JSGC_INCREMENTAL.  Is it too early to expose the empty post barriers, or should I have done this last year, before I started?
Attachment #586617 - Flags: review?(wmccloskey)
Could you make this opt-in instead of opt-out? That is, copy the root analysis one rather than the incremental one?
(Assignee)

Comment 3

5 years ago
Created attachment 593700 [details] [diff] [review]
v2: opt-in
Attachment #586617 - Attachment is obsolete: true
Attachment #586617 - Flags: review?(wmccloskey)
Attachment #593700 - Flags: review?(wmccloskey)
Attachment #593700 - Flags: review?(wmccloskey) → review+
https://hg.mozilla.org/mozilla-central/rev/44d3d54b6fc8
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla13
You need to log in before you can comment on or make changes to this bug.