summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Support/Timer.cpp
diff options
context:
space:
mode:
authorJustin Lebar <jlebar@google.com>2016-12-29 19:59:26 +0000
committerJustin Lebar <jlebar@google.com>2016-12-29 19:59:26 +0000
commit175ab74dc52f52e9d14d31d4fbf8a1e2d0995017 (patch)
tree18bff7f7252b972aa52e7e79c3fa6746eb3f69eb /llvm/lib/Support/Timer.cpp
parent291264b612415dc3462ace9aab8c713cc81de7c8 (diff)
downloadbcm5719-llvm-175ab74dc52f52e9d14d31d4fbf8a1e2d0995017.tar.gz
bcm5719-llvm-175ab74dc52f52e9d14d31d4fbf8a1e2d0995017.zip
[ADT] Delete RefCountedBaseVPTR.
Summary: This class is unnecessary. Its comment indicated that it was a compile error to allocate an instance of a class that inherits from RefCountedBaseVPTR on the stack. This may have been true at one point, but it's not today. Moreover you really do not want to allocate *any* refcounted object on the stack, vptrs or not, so if we did have a way to prevent these objects from being stack-allocated, we'd want to apply it to regular RefCountedBase too, obviating the need for a separate RefCountedBaseVPTR class. It seems that the main way RefCountedBaseVPTR provides safety is by making its subclass's destructor virtual. This may have been helpful at one point, but these days clang will emit an error if you define a class with virtual functions that inherits from RefCountedBase but doesn't have a virtual destructor. Reviewers: compnerd, dblaikie Subscribers: cfe-commits, klimek, llvm-commits, mgorny Differential Revision: https://reviews.llvm.org/D28162 llvm-svn: 290717
Diffstat (limited to 'llvm/lib/Support/Timer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud