Bug 150744

Summary: JSC should have a forceGCSlowPaths option
Product: WebKit Reporter: Saam Barati <saam>
Component: JavaScriptCoreAssignee: Saam Barati <saam>
Status: RESOLVED FIXED    
Severity: Normal CC: benjamin, commit-queue, fpizlo, ggaren, gskachkov, keith_miller, mark.lam, msaboff, oliver, sukolsak, ysuzuki
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
patch none

Description Saam Barati 2015-10-30 18:05:00 PDT
This will be really helpful for testing exception handling from lazySlowPath inside the FTL.
This will also be pretty good all around for testing our slow path code because it's so rare.

It might even be worth it to run a subset of tests under such an option.
Comment 1 Saam Barati 2015-10-30 18:59:43 PDT
Created attachment 264458 [details]
patch
Comment 2 WebKit Commit Bot 2015-10-31 02:16:25 PDT
Comment on attachment 264458 [details]
patch

Clearing flags on attachment: 264458

Committed r191840: <http://trac.webkit.org/changeset/191840>
Comment 3 WebKit Commit Bot 2015-10-31 02:16:30 PDT
All reviewed patches have been landed.  Closing bug.
Comment 4 Geoffrey Garen 2015-10-31 09:57:18 PDT
Can we call this forceAllocationSlowPaths instead?

Or, even better given our new naming convention, useAllocationFastPath=false.