WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
133070
Remove unused JSC runtime options
https://bugs.webkit.org/show_bug.cgi?id=133070
Summary
Remove unused JSC runtime options
Zsolt Borbely
Reported
2014-05-19 07:37:54 PDT
Remove unused JSC runtime options.
Attachments
Proposed patch
(3.58 KB, patch)
2014-05-19 07:46 PDT
,
Zsolt Borbely
ossy
: review+
commit-queue
: commit-queue-
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Zsolt Borbely
Comment 1
2014-05-19 07:46:10 PDT
Created
attachment 231691
[details]
Proposed patch
Csaba Osztrogonác
Comment 2
2014-05-19 08:57:45 PDT
Comment on
attachment 231691
[details]
Proposed patch View in context:
https://bugs.webkit.org/attachment.cgi?id=231691&action=review
> Source/JavaScriptCore/runtime/Options.h:-149 > - v(bool, enableExperimentalFTLCoverage, false) \
It is unused now, but we shouldn't remove it until FTL is complete. I think JSC developers will need this to add new experimental features.
> Source/JavaScriptCore/runtime/Options.h:-197 > - v(unsigned, maximumInliningDepthForMustInline, 7) \ > - v(unsigned, maximumInliningRecursionForMustInline, 3) \
These options were introduced by the cstack merge and were unused from the beginning. Were they used only for developing in the branch?
Csaba Osztrogonác
Comment 3
2014-11-28 03:24:27 PST
Comment on
attachment 231691
[details]
Proposed patch View in context:
https://bugs.webkit.org/attachment.cgi?id=231691&action=review
>> Source/JavaScriptCore/runtime/Options.h:-149 >> - v(bool, enableExperimentalFTLCoverage, false) \ > > It is unused now, but we shouldn't remove it until FTL is complete. > I think JSC developers will need this to add new experimental features.
It is still unused. Can we remove it?
>> Source/JavaScriptCore/runtime/Options.h:-197 >> - v(unsigned, maximumInliningRecursionForMustInline, 3) \ > > These options were introduced by the cstack merge and were unused from the beginning. > Were they used only for developing in the branch?
After a half year later, I still can't find any use of maximumInliningDepthForMustInline and maximumInliningRecursionForMustInline in the full git history. I think they aren't used ever. Any objection against removing them?
Csaba Osztrogonác
Comment 4
2014-12-03 03:26:39 PST
Comment on
attachment 231691
[details]
Proposed patch There were no objection, these option are really unused (and weren't used ever), so let's remove them, r=me.
WebKit Commit Bot
Comment 5
2014-12-03 03:28:18 PST
Comment on
attachment 231691
[details]
Proposed patch Rejecting
attachment 231691
[details]
from commit-queue. Failed to run "['/Volumes/Data/EWS/WebKit/Tools/Scripts/webkit-patch', '--status-host=webkit-queues.appspot.com', '--bot-id=webkit-cq-02', 'apply-attachment', '--no-update', '--non-interactive', 231691, '--port=mac']" exit_code: 2 cwd: /Volumes/Data/EWS/WebKit Last 500 characters of output: 2 (offset 13 lines). Hunk #3 succeeded at 247 (offset 15 lines). patching file Tools/ChangeLog Hunk #1 succeeded at 1 with fuzz 3. patching file Tools/Scripts/run-jsc-stress-tests Hunk #1 FAILED at 181. Hunk #2 succeeded at 616 (offset 65 lines). 1 out of 2 hunks FAILED -- saving rejects to file Tools/Scripts/run-jsc-stress-tests.rej Failed to run "[u'/Volumes/Data/EWS/WebKit/Tools/Scripts/svn-apply', '--force', '--reviewer', u'Csaba Osztrogon\xe1c']" exit_code: 1 cwd: /Volumes/Data/EWS/WebKit Full output:
http://webkit-queues.appspot.com/results/6467577131827200
Csaba Osztrogonác
Comment 6
2014-12-03 03:33:58 PST
Committed
r176716
: <
http://trac.webkit.org/changeset/176716
>
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