WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
150744
JSC should have a forceGCSlowPaths option
https://bugs.webkit.org/show_bug.cgi?id=150744
Summary
JSC should have a forceGCSlowPaths option
Saam Barati
Reported
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.
Attachments
patch
(7.11 KB, patch)
2015-10-30 18:59 PDT
,
Saam Barati
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Saam Barati
Comment 1
2015-10-30 18:59:43 PDT
Created
attachment 264458
[details]
patch
WebKit Commit Bot
Comment 2
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
>
WebKit Commit Bot
Comment 3
2015-10-31 02:16:30 PDT
All reviewed patches have been landed. Closing bug.
Geoffrey Garen
Comment 4
2015-10-31 09:57:18 PDT
Can we call this forceAllocationSlowPaths instead? Or, even better given our new naming convention, useAllocationFastPath=false.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug