Bump --enable-compiler-plugins Clang baseline?
sbergman at redhat.com
Wed Nov 4 15:31:25 UTC 2020
"Bump compiler plugins Clang baseline to 5.0.2" from about two years
ago, the baseline for (Linux) --enable-compiler-plugins builds is Clang
Wasting time yesterday with
<https://gerrit.libreoffice.org/c/core/+/105234/1..4>, tracking down why
a loplugin:toolslong false positive started to appear with old Clang, I
wondered whether we could bump once again. The benefit would be getting
rid of various #if CLANG_VERSION cruft across compilerplugins/clang/,
and potentially avoiding wasting time on similar issues in the future.
(Plus, we could revisit
"On using C++17 for compilerplugins (not possible for now)".)
The question is what the maximum Clang version would be that we could
bump to as a baseline for (Linux) --enable-compiler-plugins builds.
(For (implicit) --disable-compiler-plugins builds, baselines can stay as
they are for now. And on macOS and Windows, I think I am the only one
using --enable-compiler-plugins, and I'm using Clang trunk there anyway.)
So, what is the maximum Clang version that people would be comfortable
lode already happens to provide a recipe to install Clang 9.0.1 on
Linux. so my suggestion---absent other constraints---would be to at
least bump to Clang 9, somewhat randomly.
More information about the LibreOffice