r316858 - Driver: default to `unsigned int` `wchar_t` for ARM

2017-10-28 Thread Saleem Abdulrasool via cfe-commits
Author: compnerd Date: Sat Oct 28 23:01:14 2017 New Revision: 316858 URL: http://llvm.org/viewvc/llvm-project?rev=316858&view=rev Log: Driver: default to `unsigned int` `wchar_t` for ARM AAPCS and AAPCS64 mandate that `wchar_t` with `-fno-short-wchar` is an `unsigned int` rather than a `signed in

[PATCH] D38674: [analyzer] MisusedMovedObjectChecker: More precise warning message

2017-10-28 Thread Peter Szecsi via Phabricator via cfe-commits
This revision was automatically updated to reflect the committed changes. Closed by commit rL316852: [analyzer] MisusedMovedObjectChecker: More precise warning message (authored by szepet). Changed prior to commit: https://reviews.llvm.org/D38674?vs=118170&id=120737#toc Repository: rL LLVM

r316852 - [analyzer] MisusedMovedObjectChecker: More precise warning message

2017-10-28 Thread Peter Szecsi via cfe-commits
Author: szepet Date: Sat Oct 28 16:24:00 2017 New Revision: 316852 URL: http://llvm.org/viewvc/llvm-project?rev=316852&view=rev Log: [analyzer] MisusedMovedObjectChecker: More precise warning message Added new enum in order to differentiate the warning messages on "misusing" into 3 categories: fu

r316850 - [analyzer] MisusedMovedObjectChecker: Fix false positive on state-resetting, handling method calls on base-class sub-objects

2017-10-28 Thread Peter Szecsi via cfe-commits
Author: szepet Date: Sat Oct 28 16:09:37 2017 New Revision: 316850 URL: http://llvm.org/viewvc/llvm-project?rev=316850&view=rev Log: [analyzer] MisusedMovedObjectChecker: Fix false positive on state-resetting, handling method calls on base-class sub-objects An earlier solution from Artem r315301

[PATCH] D39382: [libunwind] Restore arch specific lastDwarfRegNum in builds without _LIBUNWIND_IS_NATIVE_ONLY

2017-10-28 Thread Martin Storsjö via Phabricator via cfe-commits
This revision was automatically updated to reflect the committed changes. Closed by commit rL316843: Restore arch specific lastDwarfRegNum in builds without… (authored by mstorsjo). Changed prior to commit: https://reviews.llvm.org/D39382?vs=120679&id=120736#toc Repository: rL LLVM https://

[libunwind] r316843 - Restore arch specific lastDwarfRegNum in builds without _LIBUNWIND_IS_NATIVE_ONLY

2017-10-28 Thread Martin Storsjo via cfe-commits
Author: mstorsjo Date: Sat Oct 28 13:19:49 2017 New Revision: 316843 URL: http://llvm.org/viewvc/llvm-project?rev=316843&view=rev Log: Restore arch specific lastDwarfRegNum in builds without _LIBUNWIND_IS_NATIVE_ONLY This restores the previous behaviour of the Registers_* classes after SVN r3167

r316836 - PR35039: Materialize temporary objects before wrapping them in an

2017-10-28 Thread Richard Smith via cfe-commits
Author: rsmith Date: Sat Oct 28 11:59:51 2017 New Revision: 316836 URL: http://llvm.org/viewvc/llvm-project?rev=316836&view=rev Log: PR35039: Materialize temporary objects before wrapping them in an OpaqueValueExpr in a GNU binary conditional expression. It's not meaningful for a non-materialized

[clang-tools-extra] r316832 - [clangd] Fix clang-tidy warnings.

2017-10-28 Thread Benjamin Kramer via cfe-commits
Author: d0k Date: Sat Oct 28 10:32:56 2017 New Revision: 316832 URL: http://llvm.org/viewvc/llvm-project?rev=316832&view=rev Log: [clangd] Fix clang-tidy warnings. No functionality change intended. Modified: clang-tools-extra/trunk/clangd/ClangdLSPServer.h clang-tools-extra/trunk/clangd/

[PATCH] D38922: [analyzer] LoopUnrolling: check the bitwidth of the used numbers (pr34943)

2017-10-28 Thread Peter Szecsi via Phabricator via cfe-commits
This revision was automatically updated to reflect the committed changes. Closed by commit rL316830: [analyzer] LoopUnrolling: check the bitwidth of the used numbers (pr34943) (authored by szepet). Changed prior to commit: https://reviews.llvm.org/D38922?vs=119019&id=120733#toc Repository: r

r316830 - [analyzer] LoopUnrolling: check the bitwidth of the used numbers (pr34943)

2017-10-28 Thread Peter Szecsi via cfe-commits
Author: szepet Date: Sat Oct 28 05:19:08 2017 New Revision: 316830 URL: http://llvm.org/viewvc/llvm-project?rev=316830&view=rev Log: [analyzer] LoopUnrolling: check the bitwidth of the used numbers (pr34943) The loop unrolling feature aims to track the maximum possible steps a loop can make. In o

[PATCH] D38921: [analyzer] LoopUnrolling: update the matched assignment operators

2017-10-28 Thread Peter Szecsi via Phabricator via cfe-commits
szepet updated this revision to Diff 120732. szepet added a comment. Updated to use a custom AST matcher for assignment operator check. (More structured and efficient.) https://reviews.llvm.org/D38921 Files: lib/StaticAnalyzer/Core/LoopUnrolling.cpp test/Analysis/loop-unrolling.cpp Index: