Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


I tried to build with Clang and --enable-werror to see if that finds
any bugs. Attached are results so far; there is still quite some to
compile and Clang also consistently crashes on a file.

All this is with self compiled Clang from trunk revision 152134 from 6
March 2012.

Only patch 6 solves a real bug, but in CLucene not LO. I sent the same
patch upstream but got no response so far.

There are quite some more "implicit conversion changes signedness"
warnings left in connectivity, is it ok to do larger changes like
patches 8 and 9 do (switch method arguments or class members from
signed to unsigned if that makes sense for example) or should I just
silence the warnings with casts?

Thanks,
Catalin

Attachment: 0001-WaE-Clang-empty-forloop-body.patch
Description: Binary data

Attachment: 0002-WaE-Clang-unused-variable.patch
Description: Binary data

Attachment: 0003-WaE-Clang-unused-variable.patch
Description: Binary data

Attachment: 0004-WaE-Clang-adding-int-to-a-string-does-not-append-to-.patch
Description: Binary data

Attachment: 0005-WaE-Clang-C-linkage-warning.patch
Description: Binary data

Attachment: 0006-WaE-patch-CLucene-to-avoid-Clang-unused-parameter-wa.patch
Description: Binary data

Attachment: 0007-WaE-Clang-expression-result-unused.patch
Description: Binary data

Attachment: 0008-WaE-Clang-implicit-conversion-changes-signedness.patch
Description: Binary data

Attachment: 0009-WaE-Clang-implicit-conversion-changes-signedness.patch
Description: Binary data


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.