summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h
diff options
context:
space:
mode:
authorRichard Smith <richard@metafoo.co.uk>2019-12-02 13:58:37 -0800
committerRichard Smith <richard@metafoo.co.uk>2019-12-02 14:41:27 -0800
commit711c669ae92658aecc6fabccc583594924bac6d7 (patch)
tree94991972527e936034e7108ad684417de658f639 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h
parent2e75681b55ab55301022533b203269f5f3d6f909 (diff)
downloadbcm5719-llvm-711c669ae92658aecc6fabccc583594924bac6d7.tar.gz
bcm5719-llvm-711c669ae92658aecc6fabccc583594924bac6d7.zip
Fix comment to more accurately describe C++ language requirements around tail padding.
Summary: As of C++ core issue 43 (http://wg21.link/cwg43), which was voted into the C++ working draft in 1999, it is not permissible to memcpy a base class subobject, even if it's of POD type, so there is no problem with reusing the tail padding of a base class. That issue was voted into the standard in DR status, so it applies retroactively to C++98 (and is in any case part of C++03). So stop suggesting that AlwaysUseTailPadding mode is non-conforming. Reviewers: rjmccall Reviewed By: rjmccall Subscribers: cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D70923
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud