Summary: | Performance optimization to patch for Bug 10773 | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Sanjay Madhav (chmmravatar) <sanjay12> | ||||
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED INVALID | ||||||
Severity: | Enhancement | ||||||
Priority: | P2 | ||||||
Version: | 420+ | ||||||
Hardware: | Mac | ||||||
OS: | OS X 10.4 | ||||||
Attachments: |
|
Description
Sanjay Madhav (chmmravatar)
2007-01-22 21:52:31 PST
Created attachment 12618 [details]
patch as described
Comment on attachment 12618 [details]
patch as described
Our convention is that the caller is responsible for checking !marked() before calling mark(), so this optimization should have no effect.
Do you know of a code path that marks a JSDocument before checking !marked()?
Oh, you're right. Nevermind this, closing it out. Just thought I had missed it and wanted to be certain. |