Bug 150744 - JSC should have a forceGCSlowPaths option
Summary: JSC should have a forceGCSlowPaths option
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Saam Barati
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-30 18:05 PDT by Saam Barati
Modified: 2015-10-31 09:57 PDT (History)
11 users (show)

See Also:

Attachments
patch (7.11 KB, patch)
2015-10-30 18:59 PDT, Saam Barati 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.