@@ -0,0 +1,180 @@
+// RUN: %check_clang_tidy -std=c++11 %s
bugprone-incorrect-enable-shared-from-this %t
PiotrZSL wrote:
Note: you could use -std=c+=11-or-later to fix problems with check in more
modern C++
https://github.com/llvm/llvm-project/pull/102299
https://github.com/PiotrZSL approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/102299
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: xtex
Date: 2025-01-01T00:29:04-08:00
New Revision: ca2ab74838c41a4146835b5bcc91ce4732273f7d
URL:
https://github.com/llvm/llvm-project/commit/ca2ab74838c41a4146835b5bcc91ce4732273f7d
DIFF:
https://github.com/llvm/llvm-project/commit/ca2ab74838c41a4146835b5bcc91ce4732273f7d.diff
LOG: [cl
https://github.com/xtexChooser edited
https://github.com/llvm/llvm-project/pull/117458
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
xtexChooser wrote:
Done
https://github.com/llvm/llvm-project/pull/117458
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
github-actions[bot] wrote:
@xtexChooser Congratulations on having your first Pull Request (PR) merged into
the LLVM Project!
Your changes will be combined with recent changes from other authors, then
tested by our [build bots](https://lab.llvm.org/buildbot/). If there is a
problem with a bu
https://github.com/MaskRay closed
https://github.com/llvm/llvm-project/pull/117458
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/mati865 created
https://github.com/llvm/llvm-project/pull/121442
Fixes https://github.com/llvm/llvm-project/issues/10148
Recently I saw a user confused by it and thought Clang was using `winpthreads`.
Note: this does not change structures like
https://github.com/llvm/llvm-p
llvmbot wrote:
@llvm/pr-subscribers-clang-driver
Author: Mateusz Mikuła (mati865)
Changes
Fixes https://github.com/llvm/llvm-project/issues/10148
Recently I saw a user confused by it and thought Clang was using `winpthreads`.
Note: this does not change structures like
https://github.com
phuang wrote:
I checked the log. And I don't think the failed test is caused by this PR.
https://github.com/llvm/llvm-project/pull/120159
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commit
@@ -619,7 +619,13 @@ class ToolChain {
virtual bool SupportsEmbeddedBitcode() const { return false; }
/// getThreadModel() - Which thread model does this target use?
- virtual std::string getThreadModel() const { return "posix"; }
+ virtual std::string getThreadModel() c
mstorsjo wrote:
As background for other reviewers: GCC can be built with either the posix or
win32 thread model. This doesn't affect code generation much (at all?), but it
does affect libgcc and libstdc++ which are built in the same GCC build.
With the win32 thread model, libgcc/libstdc++ use
@@ -4219,6 +4220,13 @@ class DecompositionDecl final
void printName(raw_ostream &OS, const PrintingPolicy &Policy) const override;
+ /// Visit the variables (if any) that hold the values of evaluating the
+ /// binding. Only present for user-defined bindings for tuple-lik
101 - 113 of 113 matches
Mail list logo