aboutsummaryrefslogtreecommitdiff
path: root/lldb/unittests/ScriptInterpreter/Python
diff options
context:
space:
mode:
authorMehdi Amini <joker.eph@gmail.com>2020-06-25 23:49:07 +0000
committerMehdi Amini <joker.eph@gmail.com>2020-06-25 23:49:07 +0000
commit4abf0243367d6e923cfa1a32e26ac3cb7787e3c9 (patch)
tree34c76fa120dfd6aae067bb49d7e59d6b4b2b530f /lldb/unittests/ScriptInterpreter/Python
parentb2303debfa63b60c21c93c318bed63341564a549 (diff)
downloadllvm-4abf0243367d6e923cfa1a32e26ac3cb7787e3c9.zip
llvm-4abf0243367d6e923cfa1a32e26ac3cb7787e3c9.tar.gz
llvm-4abf0243367d6e923cfa1a32e26ac3cb7787e3c9.tar.bz2
Remove references to the 4.0 release as a major breaking (NFC)
This is cleaning up comments (mostly in the bitcode handling) about removing some backward compatibility aspect in the 4.0 release. Historically, "4.0" was used during the development of the 3.x versions as "this future major breaking change version". At the time the major number was used to indicate the compatibility. When we reached 3.9 we decided to change the numbering, instead of going to 3.10 we went to 4.0 but after changing the meaning of the major number to not mean anything anymore with respect to bitcode backward compatibility. The current policy (https://llvm.org/docs/DeveloperPolicy.html#ir-backwards-compatibility) indicates only now: The current LLVM version supports loading any bitcode since version 3.0. Differential Revision: https://reviews.llvm.org/D82514
Diffstat (limited to 'lldb/unittests/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions