RESOLVED FIXED 162579
Add an Option to disable the CodeCache
https://bugs.webkit.org/show_bug.cgi?id=162579
Summary Add an Option to disable the CodeCache
Joseph Pecoraro
Reported 2016-09-26 15:06:58 PDT
Summary: Add an Option to disable the CodeCache Useful when benchmarking to ensure we do more parsing.
Attachments
[PATCH] Proposed Fix (3.03 KB, patch)
2016-09-26 15:09 PDT, Joseph Pecoraro
no flags
Joseph Pecoraro
Comment 1 2016-09-26 15:09:50 PDT
Created attachment 289879 [details] [PATCH] Proposed Fix
Joseph Pecoraro
Comment 2 2016-09-26 15:10:29 PDT
Comment on attachment 289879 [details] [PATCH] Proposed Fix View in context: https://bugs.webkit.org/attachment.cgi?id=289879&action=review > Source/JavaScriptCore/ChangeLog:8 > + * runtime/CodeCache.cpp: We could also use this in EvalCodeCache. Let me know if you think we should as well.
Geoffrey Garen
Comment 3 2016-09-26 15:17:07 PDT
Comment on attachment 289879 [details] [PATCH] Proposed Fix r=me
WebKit Commit Bot
Comment 4 2016-09-26 15:50:38 PDT
Comment on attachment 289879 [details] [PATCH] Proposed Fix Clearing flags on attachment: 289879 Committed r206400: <http://trac.webkit.org/changeset/206400>
WebKit Commit Bot
Comment 5 2016-09-26 15:50:43 PDT
All reviewed patches have been landed. Closing bug.
Saam Barati
Comment 6 2016-09-26 19:56:12 PDT
Comment on attachment 289879 [details] [PATCH] Proposed Fix View in context: https://bugs.webkit.org/attachment.cgi?id=289879&action=review > Source/JavaScriptCore/runtime/Options.h:391 > + v(bool, useCodeCache, true, Normal, "If false, the parser will not use the code cache.") \ Nit: This might be confusing with the word "parser" in it since the parser has its own cache and this cache is on top of the parser. I'd just say: "If false, we won't use the unlinked byte code cache" or something similar.
Saam Barati
Comment 7 2016-09-26 19:57:31 PDT
(In reply to comment #2) > Comment on attachment 289879 [details] > [PATCH] Proposed Fix > > View in context: > https://bugs.webkit.org/attachment.cgi?id=289879&action=review > > > Source/JavaScriptCore/ChangeLog:8 > > + * runtime/CodeCache.cpp: > > We could also use this in EvalCodeCache. Let me know if you think we should > as well. They're two different caches. I'd say that if we find an option for the eval code cache useful we can add it in a separate patch. I think it's good to have this option just be for the unlinked code cache.
Note You need to log in before you can comment on or make changes to this bug.