[clazy] [Bug 407623] Build with trunk LLVM/Clang is broken
https://bugs.kde.org/show_bug.cgi?id=407623 --- Comment #5 from Eugene Zelenko --- Linker error is independent for API changes. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 407625] Clang source include path in Git MonoRepo
https://bugs.kde.org/show_bug.cgi?id=407625 --- Comment #3 from Eugene Zelenko --- Problem with libc++: I build second pass LLVM/Clang with LLVM_ENABLE_LIBCXX and LLVM_ENABLE_LLD. I got a lot of unresolved symbols from libc++ when linking ClazyPlugin.so. Ether Clazy CMake should detect STL from llvm-config or reuse part of LLVM CMake files to setup STL easily. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 407623] Build with trunk LLVM/Clang is broken
https://bugs.kde.org/show_bug.cgi?id=407623 --- Comment #2 from Eugene Zelenko --- Fix is very trivial: - auto = ToolingDiag.Fix[replacement.getFilePath()]; + auto = ToolingDiag.Message.Fix[replacement.getFilePath()]; -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 407625] Clang source include path in Git MonoRepo
https://bugs.kde.org/show_bug.cgi?id=407625 --- Comment #2 from Eugene Zelenko --- Most likely it'll work, but it's not good idea to add not existing path into include paths. GCC even has -Wmissing-include-dirs. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 407625] New: Clang source include path in Git MonoRepo
https://bugs.kde.org/show_bug.cgi?id=407625
Bug ID: 407625
Summary: Clang source include path in Git MonoRepo
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: eugene.zele...@gmail.com
CC: smart...@kde.org
Target Milestone: ---
Clazy could not be built with Git MonoRepo LLVM/Clang, because different path
to Clang source include files:
My workaround was:
cmake/FindClang.cmake
- "${_llvmSourceRoot}/tools/clang/include" # source dir
+ "${_llvmSourceRoot}/../clang/include" # source dir
Ideally directory should be checked for existence to support both SubVersion
and Git source code layouts.
It may make sense to look onto Include What You Use configuration since it is
much simpler, doesn't have such problem and also support LLVM_ENABLE_LIBCXX and
LLVM_ENABLE_LLD build variants.
--
You are receiving this mail because:
You are watching all bug changes.
[clazy] [Bug 407623] New: Build with trunk LLVM/Clang is broken
https://bugs.kde.org/show_bug.cgi?id=407623 Bug ID: 407623 Summary: Build with trunk LLVM/Clang is broken Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org Target Milestone: --- src/FixItExporter.cpp:141:46: error: no member named 'Fix' in 'clang::tooling::Diagnostic' auto = ToolingDiag.Fix[replacement.getFilePath()]; ~~~ ^ -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 405951] Add -verbose command line option to clang-standalone
https://bugs.kde.org/show_bug.cgi?id=405951 --- Comment #5 from Eugene Zelenko --- (In reply to Sergio Martins from comment #4) > maybe also help the IWYU guys :) Indeed! I mentioned your workaround already since it makes IWYU works too. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 405951] Add -verbose command line option to clang-standalone
https://bugs.kde.org/show_bug.cgi?id=405951 --- Comment #3 from Eugene Zelenko --- Thank you for help! Workaround works for me. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 405951] Add -verbose command line option to clang-standalone
https://bugs.kde.org/show_bug.cgi?id=405951 --- Comment #1 from Eugene Zelenko --- See also https://github.com/include-what-you-use/include-what-you-use/issues/679 for similar problem. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 405951] New: Add -verbose command line option to clang-standalone
https://bugs.kde.org/show_bug.cgi?id=405951 Bug ID: 405951 Summary: Add -verbose command line option to clang-standalone Product: clazy Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org Target Milestone: --- I think will be good idea to have possibility to output clazy-standalone command line argument used to build particular file to troubleshoot problems. I built my project with Clang 8 and then tried to run clang-standalone using compile database. clazy-standalone complained about system headers: /usr/include/limits.h:124:16: fatal error: 'limits.h' file not found # include_next Clazy was built with same Clang 8 as my own project. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 405948] New: Detection of libz and libxml2
https://bugs.kde.org/show_bug.cgi?id=405948 Bug ID: 405948 Summary: Detection of libz and libxml2 Product: clazy Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org Target Milestone: --- I tried to build Clazy on Ubuntu where libz-dev and libxml2-dev packages were not installed. Clazy build failed only during linking. I think it'll be good idea to detect libraries availability during CMake configuration. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 403083] Build is broken with trunk Clang
https://bugs.kde.org/show_bug.cgi?id=403083
--- Comment #3 from Eugene Zelenko ---
Next changes must be made in SourceCompatibilityHelpers.h to compile Clazy:
#include
By the word, headers should be sorted alphabetically.
-if (const EnumDecl *ED = ET->getDecl()) {
+if (const clang::EnumDecl *ED = ET->getDecl()) {
-return clang::getAttr() != nullptr;
+return func->getAttr() != nullptr;
--
You are receiving this mail because:
You are watching all bug changes.
[clazy] [Bug 403083] New: Build is broken with trunk Clang
https://bugs.kde.org/show_bug.cgi?id=403083 Bug ID: 403083 Summary: Build is broken with trunk Clang Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org Target Milestone: --- src/checks/manuallevel/qrequiredresult-candidates.cpp:48:17: error: no member named 'hasUnusedResultAttr' in 'clang::CXXMethodDecl' -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 401986] Build is broken with trunk Clang
https://bugs.kde.org/show_bug.cgi?id=401986 --- Comment #2 from Eugene Zelenko --- Thank you for quick fix! -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 401986] New: Build is broken with trunk Clang
https://bugs.kde.org/show_bug.cgi?id=401986 Bug ID: 401986 Summary: Build is broken with trunk Clang Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org Target Milestone: --- src/checks/level1/range-loop.cpp:74:63: error: no member named 'getLocStart' in 'clang::Expr' endLoc = clazy::locForEndOfToken(_astContext, exp->getLocStart()); ~~~ ^ 1 error generated. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 399955] Build is broken with trunk LLVM/Clang
https://bugs.kde.org/show_bug.cgi?id=399955 --- Comment #6 from Eugene Zelenko --- Builds OK now. By the word, I spotted include in Clazy.cpp. WIll be good idea to run Clang-tidy modernize-deprecated-headers, and probably other modernize and readability checks. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 399955] Build is broken with trunk LLVM/Clang
https://bugs.kde.org/show_bug.cgi?id=399955 --- Comment #4 from Eugene Zelenko --- Please add llvm:: before StringRef in variable declarations in all three files to fix build. ext/alloc_traits.h should be removed from Clazy.cpp, because it's STL internals which may vary between libstdc++/libc++. Clazy/src/Clazy.cpp:25:10: fatal error: 'ext/alloc_traits.h' file not found #include Also, IWYU added LLVM/Clang include directives "" when Clazy code base uses <>, so order of headers is affected. Sometimes empty line separates headers and mess up their order. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 399955] Build is broken with trunk LLVM/Clang
https://bugs.kde.org/show_bug.cgi?id=399955 --- Comment #2 from Eugene Zelenko --- Thank you for help! -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 399955] New: Build is broken with trunk LLVM/Clang
https://bugs.kde.org/show_bug.cgi?id=399955 Bug ID: 399955 Summary: Build is broken with trunk LLVM/Clang Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org Target Milestone: --- Build is broken with trunk LLVM/Clang. I think will be good idea to run Include What You Use over Clazy code. In file included from src/checks/detachingbase.cpp:28: In file included from src/QtUtils.h:28: src/MacroUtils.h:66:9: error: unknown type name 'StringRef' StringRef macro = clang::Lexer::getImmediateMacroName(loc, context->getSourceManager(), context->getLangOpts()); ^ In file included from src/checks/detachingbase.cpp:28: In file included from src/QtUtils.h:29: src/FunctionUtils.h:107:5: error: unknown type name 'StringRef' StringRef methodName = method->getName(); ^ In file included from src/checks/manuallevel/container-inside-loop.cpp:23: src/ClazyContext.h:127:9: error: unknown type name 'StringRef' StringRef fileName((*file)->getName()); ^ -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 398851] Build is broken with trunk Clang
https://bugs.kde.org/show_bug.cgi?id=398851 --- Comment #2 from Eugene Zelenko --- Thank you for quick fix! -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 398851] New: Build is broken with trunk Clang
https://bugs.kde.org/show_bug.cgi?id=398851 Bug ID: 398851 Summary: Build is broken with trunk Clang Product: clazy Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org Target Milestone: --- Build is broken with trunk Clang because of renamed getLocStart(),/getLocEnd() methods: src/StringUtils.h:183:30: error: no member named 'getLocStart' in 'clang::Stmt' -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 393745] Build is broken with trunk LLVM/Clang
https://bugs.kde.org/show_bug.cgi?id=393745 Eugene Zelenko <eugene.zele...@gmail.com> changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #2 from Eugene Zelenko <eugene.zele...@gmail.com> --- Actually trunk LLVM/Clang version is 7. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 393745] New: Build is broken with trunk LLVM/Clang
https://bugs.kde.org/show_bug.cgi?id=393745
Bug ID: 393745
Summary: Build is broken with trunk LLVM/Clang
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: eugene.zele...@gmail.com
CC: smart...@kde.org
Target Milestone: ---
Build with with trunk LLVM/Clang become broken yesterday:
Clazy/src/checks/level2/old-style-connect.cpp:232:52: error: no member named
'first' in 'clang::CharSourceRange'
SourceRange range = SourceRange(expansionRange.first,
expansionRange.second);
~~ ^
Clazy/src/checks/level2/old-style-connect.cpp:232:74: error: no member named
'second' in 'clang::CharSourceRange';
did you mean 'setEnd'?
SourceRange range = SourceRange(expansionRange.first,
expansionRange.second);
^~
setEnd
llvm-svn.src/tools/clang/include/clang/Basic/SourceLocation.h:267:8: note:
'setEnd' declared here
void setEnd(SourceLocation e) { Range.setEnd(e); }
^
Clazy/src/checks/level2/old-style-connect.cpp:397:60: error: no member named
'first' in 'clang::CharSourceRange'
SourceRange range = SourceRange(expansionRange.first,
expansionRange.second);
~~ ^
Clazy/src/checks/level2/old-style-connect.cpp:397:82: error: no member named
'second' in 'clang::CharSourceRange';
did you mean 'setEnd'?
SourceRange range = SourceRange(expansionRange.first,
expansionRange.second);
^~
setEnd
llvm-svn.src/tools/clang/include/clang/Basic/SourceLocation.h:267:8: note:
'setEnd' declared here
void setEnd(SourceLocation e) { Range.setEnd(e); }
^
--
You are receiving this mail because:
You are watching all bug changes.
[clazy] [Bug 381775] Clazy build is broken because of missing clanglazy_export.h
https://bugs.kde.org/show_bug.cgi?id=381775 Eugene Zelenko <eugene.zele...@gmail.com> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Eugene Zelenko <eugene.zele...@gmail.com> --- Sorry, I tweaked CMakeLists.txt to be able to build with LLVM/Clang source tree (not installed version))build, so I missed CMAKE_BINARY_DIR in include list. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 381775] New: Clazy build is broken because of missing clanglazy_export.h
https://bugs.kde.org/show_bug.cgi?id=381775 Bug ID: 381775 Summary: Clazy build is broken because of missing clanglazy_export.h Product: clazy Version: unspecified Platform: RedHat RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org Target Milestone: --- Clazy build is broken because of missing clanglazy_export.h: In file included from Clazy/src/Clazy.cpp:26: Clazy/src/Clazy.h:28:10: fatal error: 'clanglazy_export.h' file not found #include "clanglazy_export.h" clanglazy_export.h is listed in .gitignore. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 375820] Build with trunk LLVM/Clang is broken
https://bugs.kde.org/show_bug.cgi?id=375820 --- Comment #3 from Eugene Zelenko <eugene.zele...@gmail.com> --- Thank you for quick fix, Sergio! -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 375820] New: Build with trunk LLVM/Clang is broken
https://bugs.kde.org/show_bug.cgi?id=375820 Bug ID: 375820 Summary: Build with trunk LLVM/Clang is broken Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org Target Milestone: --- I got next errors when built Clazy with trunck LLVM/Clang. I think will be good idea to run Include What You Use to reduce chance of similar issues in future. Clazy/checkmanager.h:116:41: error: member access into incomplete type 'const clang::PreprocessorOptions' return !ci.getPreprocessorOpts().ImplicitPCHInclude.empty(); ^ tools/clang/include/clang/Frontend/CompilerInvocation.h:35:7: note: forward declaration of 'clang::PreprocessorOptions' class PreprocessorOptions; ^ In file included from /grid/cic/nsd-farm2/data/zelenko/LLVM.svn/Clazy/checkbase.cpp:27: Clazy/checkmanager.h:116:41: error: member access into incomplete type 'const clang::PreprocessorOptions' return !ci.getPreprocessorOpts().ImplicitPCHInclude.empty(); ^ tools/clang/include/clang/Frontend/CompilerInvocation.h:35:7: note: forward declaration of 'clang::PreprocessorOptions' class PreprocessorOptions; -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 368361] CMake variable to control headers installation
https://bugs.kde.org/show_bug.cgi?id=368361 --- Comment #2 from Eugene Zelenko <eugene.zele...@gmail.com> --- See http://llvm.org/klaus/lldb/blob/master/cmake/modules/LLDBConfig.cmake as example. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 365880] New: Build with trunk LLVM/Clang is broken
https://bugs.kde.org/show_bug.cgi?id=365880 Bug ID: 365880 Summary: Build with trunk LLVM/Clang is broken Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org LLVM/Clang 3.9 branch was created yesterday and version was switched to 4.0, so build fails in conditions LLVM_VERSION_MAJOR == 3 && LLVM_VERSION_MINOR > (particular number). -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 364731] New: Build with trunk LLVM/Clang is broken
https://bugs.kde.org/show_bug.cgi?id=364731 Bug ID: 364731 Summary: Build with trunk LLVM/Clang is broken Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org clang::FunctionDecl interface was changed in r273647, so params() looks to be renamed to parameters(). I think will be good idea to create wrapper class to avoid large number of preprocessor's conditional statements in multiple files. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361504] New: dlopen()/dlclose() and shared object usage check
https://bugs.kde.org/show_bug.cgi?id=361504 Bug ID: 361504 Summary: dlopen()/dlclose() and shared object usage check Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: eugene.zele...@gmail.com I encountered situation when shared library was opened dlopen(), dlsym() was use to get function pointer, that function register function and data addresses in global data structure, dlclose() was called, but functions and data from shared library were used after that. I'll be great if Valgrind will detect such invalid coding patterns, but I'm not sure if dl allow to get data/code segments addresses as well as reserve closed segments from re-using for later check in Valgrind. -- You are receiving this mail because: You are watching all bug changes.
