|
|
Created:
3 years, 9 months ago by Mostyn Bramley-Moore Modified:
3 years, 9 months ago CC:
chromium-reviews, blink-reviews-css, dglazkov+blink, apavlov+blink_chromium.org, darktears, blink-reviews, blink-reviews-wtf_chromium.org, Mikhail, rwlbuis Target Ref:
refs/heads/master Project:
chromium Visibility:
Public. |
DescriptionLinkedStack.h is no longer used, remove it
BUG=none
NO_DEPENDENCY_CHECKS=true
Review-Url: https://codereview.chromium.org/2761853003
Cr-Commit-Position: refs/heads/master@{#458376}
Committed: https://chromium.googlesource.com/chromium/src/+/951df7be3b2b83f682351f98300354f7a2807be9
Patch Set 1 #Patch Set 2 : add comment in HeapLinkedStack.h #Patch Set 3 : rebase on master, avoid spurious patch dep #
Messages
Total messages: 33 (17 generated)
The CQ bit was checked by mostynb@opera.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== LinkedStack.h is no longer used, remove it ========== to ========== LinkedStack.h is no longer used, remove it BUG=none ==========
mostynb@opera.com changed reviewers: + haraken@chromium.org, sigbjornf@opera.com
@haraken: please take a look at this dead code removal.
dglazkov@chromium.org changed reviewers: + dglazkov@chromium.org
lgtm
sigbjornf@opera.com changed reviewers: - dglazkov@chromium.org
Keep HeapLinkedStack<>, but not LinkedStack<> ?
On 2017/03/20 20:57:31, sof wrote: > Keep HeapLinkedStack<>, but not LinkedStack<> ? HeapLinkedStack is still used in RuleSet.cpp and HeapTest.cpp.
The CQ bit was unchecked by mostynb@opera.com
The CQ bit was checked by mostynb@opera.com
The CQ bit was unchecked by commit-bot@chromium.org
This CL has an open dependency (Issue 1505823003 Patch 120001). Please resolve the dependency and try again. If you are sure that there is no real dependency, please use one of the options listed in https://goo.gl/9Es4OR to land the CL.
On 2017/03/20 20:58:51, Mostyn Bramley-Moore wrote: > On 2017/03/20 20:57:31, sof wrote: > > Keep HeapLinkedStack<>, but not LinkedStack<> ? > > HeapLinkedStack is still used in RuleSet.cpp and HeapTest.cpp. Yes, so it makes some sense to keep a symmetric set (Heap and not) around.
On 2017/03/20 21:00:36, sof wrote: > > > Keep HeapLinkedStack<>, but not LinkedStack<> ? > > > > HeapLinkedStack is still used in RuleSet.cpp and HeapTest.cpp. > > Yes, so it makes some sense to keep a symmetric set (Heap and not) around. Even if LinkedStack is no longer tested (beyond compilation testing)? It looks like HeapLinkedStack is currently only used as intermediate storage before compacting them into HeapTerminatedArray's. I could investigate cutting out the middleman, if you think it's worthwhile (and can help me figure out how to mem + perf test such a change). If not, I can at least add some documentation to these classes.
On 2017/03/20 23:04:15, Mostyn Bramley-Moore wrote: > On 2017/03/20 21:00:36, sof wrote: > > > > Keep HeapLinkedStack<>, but not LinkedStack<> ? > > > > > > HeapLinkedStack is still used in RuleSet.cpp and HeapTest.cpp. > > > > Yes, so it makes some sense to keep a symmetric set (Heap and not) around. > > Even if LinkedStack is no longer tested (beyond compilation testing)? > > It looks like HeapLinkedStack is currently only used as intermediate storage > before compacting them into HeapTerminatedArray's. I could investigate cutting > out the middleman, if you think it's worthwhile (and can help me figure out how > to mem + perf test such a change). If not, I can at least add some > documentation to these classes. +1 to removing HeapLinkedStack. Reducing # of data structures in the code base sounds nice.
On 2017/03/20 23:33:54, haraken wrote: > On 2017/03/20 23:04:15, Mostyn Bramley-Moore wrote: > > On 2017/03/20 21:00:36, sof wrote: > > > > > Keep HeapLinkedStack<>, but not LinkedStack<> ? > > > > > > > > HeapLinkedStack is still used in RuleSet.cpp and HeapTest.cpp. > > > > > > Yes, so it makes some sense to keep a symmetric set (Heap and not) around. > > > > Even if LinkedStack is no longer tested (beyond compilation testing)? > > > > It looks like HeapLinkedStack is currently only used as intermediate storage > > before compacting them into HeapTerminatedArray's. I could investigate > cutting > > out the middleman, if you think it's worthwhile (and can help me figure out > how > > to mem + perf test such a change). If not, I can at least add some > > documentation to these classes. > > +1 to removing HeapLinkedStack. Reducing # of data structures in the code base > sounds nice. RuleSets switched to this stack abstraction to reduce allocation footprint (i.e., used instead of Vector), iirc. If HeapLinkedStack<> could have a comment next to it to say that it was based on wtf/LinkedStack.h, that would be preferable -- giving enough of a hint to avoid re-invention if someone should need the non-heap alternative at some point.
Description was changed from ========== LinkedStack.h is no longer used, remove it BUG=none ========== to ========== LinkedStack.h is no longer used, remove it BUG=none NO_DEPENDENCY_CHECKS=true ==========
On 2017/03/21 06:36:53, sof wrote: > RuleSets switched to this stack abstraction to reduce allocation footprint > (i.e., used instead of Vector), iirc. > > If HeapLinkedStack<> could have a comment next to it to say that it was based on > wtf/LinkedStack.h, that would be preferable -- giving enough of a hint to avoid > re-invention if someone should need the non-heap alternative at some point. Added such a comment in HeapLinkedStack.h instead- how does this look?
lgtm
The CQ bit was checked by mostynb@opera.com
The patchset sent to the CQ was uploaded after l-g-t-m from dglazkov@chromium.org Link to the patchset: https://codereview.chromium.org/2761853003/#ps20001 (title: "add comment in HeapLinkedStack.h")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
The CQ bit was checked by mostynb@opera.com
The patchset sent to the CQ was uploaded after l-g-t-m from sigbjornf@opera.com, dglazkov@chromium.org Link to the patchset: https://codereview.chromium.org/2761853003/#ps40001 (title: "rebase on master, avoid spurious patch dep?")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
LGTM
CQ is committing da patch. Bot data: {"patchset_id": 40001, "attempt_start_ts": 1490091152506860, "parent_rev": "558e1295655666d3e80365af85de9b27b912eb6d", "commit_rev": "951df7be3b2b83f682351f98300354f7a2807be9"}
Message was sent while issue was closed.
Description was changed from ========== LinkedStack.h is no longer used, remove it BUG=none NO_DEPENDENCY_CHECKS=true ========== to ========== LinkedStack.h is no longer used, remove it BUG=none NO_DEPENDENCY_CHECKS=true Review-Url: https://codereview.chromium.org/2761853003 Cr-Commit-Position: refs/heads/master@{#458376} Committed: https://chromium.googlesource.com/chromium/src/+/951df7be3b2b83f682351f983003... ==========
Message was sent while issue was closed.
Committed patchset #3 (id:40001) as https://chromium.googlesource.com/chromium/src/+/951df7be3b2b83f682351f983003... |