Author: Prabhu Rajasekaran
Date: 2025-07-22T17:57:17-07:00
New Revision: 471e59b858b1d2ee844cb527522e60ed03a1a1dc
URL:
https://github.com/llvm/llvm-project/commit/471e59b858b1d2ee844cb527522e60ed03a1a1dc
DIFF:
https://github.com/llvm/llvm-project/commit/471e59b858b1d2ee844cb527522e60ed03a1a1dc.
https://github.com/Prabhuk closed
https://github.com/llvm/llvm-project/pull/150115
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/Prabhuk edited
https://github.com/llvm/llvm-project/pull/150115
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Prabhuk wrote:
> looks ok to me. Or do you think it would make more sense to put this check in
> `isKnownWindowsMSVCEnvironment()`?
Thanks Amy! We want to make decisions for UEFI environment without MSVC/windows
assumptions. It was one of the motivations for introducing the UEFI target
triple
https://github.com/hnrklssn closed
https://github.com/llvm/llvm-project/pull/149951
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Doug Gregor
Date: 2025-07-22T17:49:13-07:00
New Revision: 8c26858f1a8bc5796c493f4f720552edbcb09fb4
URL:
https://github.com/llvm/llvm-project/commit/8c26858f1a8bc5796c493f4f720552edbcb09fb4
DIFF:
https://github.com/llvm/llvm-project/commit/8c26858f1a8bc5796c493f4f720552edbcb09fb4.diff
L
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-x86_64-debian`
running on `lldb-x86_64-debian` while building `clang` at step 6 "test".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/162/builds/27377
Here is the relevant piece of the build lo
@@ -4886,6 +4886,10 @@ Action *Driver::BuildOffloadingActions(Compilation &C,
// individually.
for (Action *&A : DeviceActions) {
if ((A->getType() != types::TY_Object &&
+ !(A->getOffloadingToolChain() &&
+ A->getOffloadingToolChain()->getTr
https://github.com/shafik commented:
Next time can you add more details to the summary, these are especially helpful
for downstream folks but also for reviewers. Something along the lines of
"Perform a null check in SanitizerAnnotateDebugInfo for the result of
getCurrentDebugLocation".
https:
https://github.com/vsapsai closed
https://github.com/llvm/llvm-project/pull/149857
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Volodymyr Sapsai
Date: 2025-07-22T20:15:54-04:00
New Revision: dbc41dd5d827a3e13625a66fd2bfa83a8a4dfe83
URL:
https://github.com/llvm/llvm-project/commit/dbc41dd5d827a3e13625a66fd2bfa83a8a4dfe83
DIFF:
https://github.com/llvm/llvm-project/commit/dbc41dd5d827a3e13625a66fd2bfa83a8a4dfe83.di
@@ -595,6 +595,10 @@ struct GH99278_2 {
} f;
};
GH99278_2 e;
+void GH99278_3(int(*p)[]) {
+ delete p;
+ // expected-warning@-1 {{'delete' applied to a pointer-to-array type 'int
(*)[]' treated as 'delete[]'}}
+};
hvdijk wrote:
I've changed the array tests
https://github.com/hvdijk updated
https://github.com/llvm/llvm-project/pull/149406
>From 94e652bc0bd6a04ef61a9f9b703257d464c7b714 Mon Sep 17 00:00:00 2001
From: Harald van Dijk
Date: Thu, 17 Jul 2025 21:47:30 +0100
Subject: [PATCH 1/7] More fixes for P3144R2 implementation
P3144R2 made it ill-
https://github.com/hvdijk updated
https://github.com/llvm/llvm-project/pull/149406
>From 94e652bc0bd6a04ef61a9f9b703257d464c7b714 Mon Sep 17 00:00:00 2001
From: Harald van Dijk
Date: Thu, 17 Jul 2025 21:47:30 +0100
Subject: [PATCH 1/6] More fixes for P3144R2 implementation
P3144R2 made it ill-
https://github.com/aadanen updated
https://github.com/llvm/llvm-project/pull/149396
>From f3fbebdd6d940d36561ccf5177510095ba05077e Mon Sep 17 00:00:00 2001
From: Aaron Danen
Date: Wed, 16 Jul 2025 19:44:58 -0700
Subject: [PATCH 1/5] clarified %undo error msg in clang-repl
used grep -r "Too man
@@ -679,6 +685,50 @@ bool SemaRISCV::CheckBuiltinFunctionCall(const TargetInfo
&TI,
return CheckVSetVL(1, 2);
case RISCVVector::BI__builtin_rvv_vsetvlimax:
return CheckVSetVL(0, 1);
+ case RISCVVector::BI__builtin_rvv_sf_vsettnt:
+ case RISCVVector::BI__builtin_rvv
https://github.com/vsapsai updated
https://github.com/llvm/llvm-project/pull/149857
>From afb15bdb129365564591b17986f45e63542da24e Mon Sep 17 00:00:00 2001
From: Volodymyr Sapsai
Date: Mon, 21 Jul 2025 13:31:56 -0400
Subject: [PATCH] [clang][deps] Add a release note for fixing crashes in
`clan
@@ -595,6 +595,10 @@ struct GH99278_2 {
} f;
};
GH99278_2 e;
+void GH99278_3(int(*p)[]) {
+ delete p;
+ // expected-warning@-1 {{'delete' applied to a pointer-to-array type 'int
(*)[]' treated as 'delete[]'}}
+};
hvdijk wrote:
> The general issue here is
amykhuang wrote:
looks ok to me. Or do you think it would make more sense to put this check in
`isKnownWindowsMSVCEnvironment()`?
https://github.com/llvm/llvm-project/pull/150115
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.l
aadanen wrote:
@DavidSpickett I applied clang-format and I think everything is looking good.
Do I need to do anything else? Or is squashing the commits and merging up to
someone with write permissions?
Also, thanks a lot for the help. I plan to find a new issue to work on soon.
Thanks for off
https://github.com/aadanen updated
https://github.com/llvm/llvm-project/pull/149396
>From f3fbebdd6d940d36561ccf5177510095ba05077e Mon Sep 17 00:00:00 2001
From: Aaron Danen
Date: Wed, 16 Jul 2025 19:44:58 -0700
Subject: [PATCH 1/5] clarified %undo error msg in clang-repl
used grep -r "Too man
github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff HEAD~1 HEAD --extensions cpp --
clang/test/Analysis/model-file-missing.cpp
clang/lib
https://github.com/sarnex approved this pull request.
https://github.com/llvm/llvm-project/pull/150110
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/shafik edited
https://github.com/llvm/llvm-project/pull/150088
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -14631,8 +14631,9 @@ EvaluateComparisonBinaryOperator(EvalInfo &Info, const
BinaryOperator *E,
// - Otherwise pointer comparisons are unspecified.
if (!LHSDesignator.Invalid && !RHSDesignator.Invalid && IsRelational) {
bool WasArrayIndex;
- unsigned Misma
https://github.com/shafik approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/150088
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
dyung wrote:
@sivadeilra the tests are still failing at least on my MacOS bot after the fix
in 9a7a6b24f8c88718ef1eea57bed07332e751c027. Can you take a look?
https://lab.llvm.org/buildbot/#/builders/190/builds/23988
```
TEST 'Clang :: CodeGenCXX/microsoft-abi-eh-disabled.c
dhruvachak wrote:
@usx95 Build of https://github.com/ROCm/composable_kernel is failing with the
same crash. -Weverything is used there as well.
Can you please fix the problem or revert?
https://github.com/llvm/llvm-project/pull/148222
___
cfe-commits
farzonl wrote:
This change will absolutely fix the issue, I was advised on my few attempts
that we want to be able to keep the same name and the fix should be in cmake
and not a file rename.
For example We have many `AMDGPU.cpp`
- clang/lib/Basic/Targets/AMDGPU.cpp
- clang/lib/CodeGen/Targets/
https://github.com/jroelofs approved this pull request.
https://github.com/llvm/llvm-project/pull/150079
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
badumbatish wrote:
thanks Paulo, will rebase this for a precommit test for clearer demonstration
https://github.com/llvm/llvm-project/pull/148935
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cf
llvmbot wrote:
@llvm/pr-subscribers-backend-risc-v
Author: Alexandros Lamprineas (labrinea)
Changes
FMV priority is the returned value of a polymorphic function. On RISC-V and X86
targets a 32-bit value is enough. On AArch64 we currently need 64 bits and we
will soon exceed that. APInt s
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Alexandros Lamprineas (labrinea)
Changes
FMV priority is the returned value of a polymorphic function. On RISC-V and X86
targets a 32-bit value is enough. On AArch64 we currently need 64 bits and we
will soon exceed that. APInt seems to b
https://github.com/labrinea created
https://github.com/llvm/llvm-project/pull/150079
FMV priority is the returned value of a polymorphic function. On RISC-V and X86
targets a 32-bit value is enough. On AArch64 we currently need 64 bits and we
will soon exceed that. APInt seems to be a suitable
https://github.com/adrian-prantl approved this pull request.
https://github.com/llvm/llvm-project/pull/149897
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -311,6 +312,115 @@ void CIRGenFunction::emitInitializerForField(FieldDecl
*field, LValue lhs,
assert(!cir::MissingFeatures::requiresCleanups());
}
+/// Emit a loop to call a particular constructor for each of several members
+/// of an array.
+///
+/// \param ctor the co
https://github.com/andykaylor edited
https://github.com/llvm/llvm-project/pull/149142
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -22,15 +24,97 @@ struct LoweringPreparePass : public
LoweringPrepareBase {
void runOnOperation() override;
void runOnOp(Operation *op);
+ void lowerArrayCtor(ArrayCtor op);
};
} // namespace
-void LoweringPreparePass::runOnOp(Operation *op) {}
+void LoweringPrep
@@ -0,0 +1,93 @@
+// RUN: %clang_cc1 -triple x86_64-unknown-linux-gnu -Wno-unused-value
-fclangir -emit-cir -mmlir --mlir-print-ir-before=cir-lowering-prepare %s -o -
2>&1 | FileCheck --check-prefixes=CIR-BEFORE-LPP %s
+// RUN: %clang_cc1 -triple x86_64-unknown-linux-gnu -Wno-u
@@ -0,0 +1,93 @@
+// RUN: %clang_cc1 -triple x86_64-unknown-linux-gnu -Wno-unused-value
-fclangir -emit-cir -mmlir --mlir-print-ir-before=cir-lowering-prepare %s -o -
2>&1 | FileCheck --check-prefixes=CIR-BEFORE-LPP %s
+// RUN: %clang_cc1 -triple x86_64-unknown-linux-gnu -Wno-u
https://github.com/andykaylor approved this pull request.
lgtm, with one nit remaining and a couple of test requests
https://github.com/llvm/llvm-project/pull/149142
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin
https://github.com/Prabhuk edited
https://github.com/llvm/llvm-project/pull/87574
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/sivadeilra closed
https://github.com/llvm/llvm-project/pull/150067
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/pawosm-arm approved this pull request.
I've tried this commit, it makes gromacs buildable again!
https://github.com/llvm/llvm-project/pull/149592
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/
https://github.com/dpaoliello updated
https://github.com/llvm/llvm-project/pull/150068
>From 3c087665701751fb4733060551b04542c419cb46 Mon Sep 17 00:00:00 2001
From: Daniel Paoliello
Date: Tue, 22 Jul 2025 10:17:02 -0700
Subject: [PATCH] Fixes to unblock building LLVM and Clang as Arm64EC
---
Author: Michael Liao
Date: 2025-07-22T13:36:04-04:00
New Revision: 9a7a6b24f8c88718ef1eea57bed07332e751c027
URL:
https://github.com/llvm/llvm-project/commit/9a7a6b24f8c88718ef1eea57bed07332e751c027
DIFF:
https://github.com/llvm/llvm-project/commit/9a7a6b24f8c88718ef1eea57bed07332e751c027.diff
@@ -743,28 +808,81 @@ static bool hasUnsafeFormatOrSArg(const CallExpr *Call,
const Expr *&UnsafeArg,
const CallExpr *Call;
unsigned FmtArgIdx;
const Expr *&UnsafeArg;
+ASTContext &Ctx;
+
+// Returns an `Expr` representing the precision if specified, null
+
github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff HEAD~1 HEAD --extensions cpp --
llvm/lib/TargetParser/Host.cpp llvm/tools/llvm-exeges
cachemeifyoucan wrote:
> & then for now, in your use case, you'd be using the cc1 flag via -Xclang,
> etc?
Our explicit module build comes from dependency scanner, where it can generate
the cc1 arguments we want to achieve empty compilation directory if needed.
https://github.com/llvm/llvm-p
llvmbot wrote:
@llvm/pr-subscribers-platform-windows
Author: Daniel Paoliello (dpaoliello)
Changes
These changes allow LLVM and Clang to be built with Clang targeting Arm64EC
using the MSVC linker.
Built with these options:
```
-DLLVM_ENABLE_PROJECTS="clang"
-DLLVM_HOST_TRIPLE=arm64ec-pc
jeremyd2019 wrote:
This change seems to be causing a regression for MinGW and Cygwin targets, see
#149639
https://github.com/llvm/llvm-project/pull/130255
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/l
https://github.com/dpaoliello created
https://github.com/llvm/llvm-project/pull/150068
These changes allow LLVM and Clang to be built with Clang targeting Arm64EC
using the MSVC linker.
Built with these options:
```
-DLLVM_ENABLE_PROJECTS="clang"
-DLLVM_HOST_TRIPLE=arm64ec-pc-windows-msvc
-DCM
dwblaikie wrote:
> Here is idea to not to add a new option. I am going to remove the fallback in
> CodeGen but make sure clang-driver does the fallback computation and clang
> cc1 will always respect that decision from clang-driver. In that case, it is
> a behavior change for cc1 flag, but not
cachemeifyoucan wrote:
Here is idea to not to add a new option. I am going to remove the fallback in
CodeGen but make sure clang-driver does the fallback computation and clang cc1
will always respect that decision from clang-driver. In that case, it is a
behavior change for cc1 flag, but not f
https://github.com/jansvoboda11 closed
https://github.com/llvm/llvm-project/pull/149904
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Jan Svoboda
Date: 2025-07-22T10:10:39-07:00
New Revision: aa1b416065ec615e93c496bbb43c7c006a04553e
URL:
https://github.com/llvm/llvm-project/commit/aa1b416065ec615e93c496bbb43c7c006a04553e
DIFF:
https://github.com/llvm/llvm-project/commit/aa1b416065ec615e93c496bbb43c7c006a04553e.diff
L
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: None (sivadeilra)
Changes
Fix `-` vs `/` paths for non-Windows platforms for integration tests in #144745
---
Full diff: https://github.com/llvm/llvm-project/pull/150067.diff
2 Files Affected:
- (modified) clang/test/CodeGenCXX/microso
https://github.com/sivadeilra created
https://github.com/llvm/llvm-project/pull/150067
Fix `-` vs `/` paths for non-Windows platforms for integration tests in #144745
>From ac5b66f4069649cba72aca55c37eb609fa8eff3a Mon Sep 17 00:00:00 2001
From: Arlie Davis
Date: Tue, 22 Jul 2025 10:08:23 -070
cachemeifyoucan wrote:
I am not planning to merge yet until debug info people approves the direction.
Like you said, I considered `-fdebug-compilation-dir=` option but it is
actually altering the behavior if I want to achieve empty compilation
directory. The underlying implementation can be tw
https://github.com/mmha updated https://github.com/llvm/llvm-project/pull/149142
>From 9814dc290952184c3a1080ea49ddd29b603ecdae Mon Sep 17 00:00:00 2001
From: Morris Hafner
Date: Wed, 16 Jul 2025 18:48:52 +0200
Subject: [PATCH 1/5] [CIR] Add support for array constructors
This patch upstreams s
https://github.com/evelez7 updated
https://github.com/llvm/llvm-project/pull/149588
>From a2851dd55f354bcdcb2e7b83b73dd16d039a3eda Mon Sep 17 00:00:00 2001
From: Erick Velez
Date: Fri, 18 Jul 2025 13:58:14 -0700
Subject: [PATCH] [clang-doc] refactor JSON for better Mustache compatibility
---
sivadeilra wrote:
@jansvoboda11 Can you verify that this change:
```
// RUN: %clang_cl -c --target=x86_64-windows-msvc /EHs-c- -O2 /GS- \
// RUN: -Xclang=-import-call-optimization \
// RUN: /clang:-S /clang:-o- -- %s 2>&1 \
// RUN: | FileCheck %s
```
(inserting `--` before `%s`) fixes the
dyung wrote:
> This is causing failures on my macOS machine that uses paths starting with
> "/Users":
These test failures also appeared on my macOS bot:
https://lab.llvm.org/buildbot/#/builders/190/builds/23983
https://github.com/llvm/llvm-project/pull/144745
_
dwblaikie wrote:
I think at least with Bazel we use `-fdebug-compilation-dir=/proc/cwd` to
create build-path-agnostic builds. Is that something you folks can use, rather
than adding this new option? Or is there some other way we could make
`-fdebug-compilation-dir` address this? (like differen
sivadeilra wrote:
Looking at this now, along with a test failure on AArch64.
https://github.com/llvm/llvm-project/pull/144745
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jansvoboda11 wrote:
This is causing failures on my macOS machine that uses paths starting with
"/Users":
```
FAIL: Clang :: CodeGenCXX/microsoft-abi-eh-disabled.cpp (21998 of 22004)
TEST 'Clang :: CodeGenCXX/microsoft-abi-eh-disabled.cpp'
FAILED
Exit Co
dwblaikie wrote:
> According to my understanding, this issue happens because when a standard
> library header like uses a function-local lambda, the compiler generates a
> closure type for that lambda sometimes this closure type gets added to the
> debug info without including its captured var
https://github.com/andykaylor approved this pull request.
lgtm if @xlauko is satisfied.
https://github.com/llvm/llvm-project/pull/149717
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-armv8-quick` running
on `linaro-clang-armv8-quick` while building `clang,llvm` at step 5 "ninja
check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/154/builds/19094
Here is the relevant p
sivadeilra wrote:
Created issue #150057 for follow-up improvements.
https://github.com/llvm/llvm-project/pull/144745
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-aarch64-quick`
running on `linaro-clang-aarch64-quick` while building `clang,llvm` at step 5
"ninja check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/65/builds/19986
Here is the relevan
@@ -710,17 +704,25 @@ static bool forEachDriverJob(
static bool createAndRunToolInvocation(
std::vector CommandLine, DependencyScanningAction &Action,
-FileManager &FM,
+IntrusiveRefCntPtr FS,
std::shared_ptr &PCHContainerOps,
DiagnosticsEngine &Diags, De
https://github.com/benlangmuir approved this pull request.
https://github.com/llvm/llvm-project/pull/149904
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,310 @@
+// RUN: %clang_cc1 -triple x86_64-unknown-linux-gnu -fclangir -emit-cir -mmlir
--mlir-print-ir-before=cir-canonicalize -o %t.cir %s 2>&1 | FileCheck
--check-prefix=CIR-BEFORE %s
+// RUN: %clang_cc1 -triple x86_64-unknown-linux-gnu -fclangir -emit-cir -mmlir
-
https://github.com/AmrDeveloper updated
https://github.com/llvm/llvm-project/pull/149717
>From 8a3e3e87ef31fd347eb70f853a112af5d3c11630 Mon Sep 17 00:00:00 2001
From: AmrDeveloper
Date: Sun, 20 Jul 2025 16:58:13 +0200
Subject: [PATCH 1/7] [CIR] Upstream Cast kinds for ComplexType
---
clang/in
llvmbot wrote:
/pull-request llvm/llvm-project#150056
https://github.com/llvm/llvm-project/pull/149076
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
github-actions[bot] wrote:
:warning: undef deprecator found issues in your code. :warning:
You can test this locally with the following command:
``bash
git diff -U0 --pickaxe-regex -S
'([^a-zA-Z0-9#_-]undef[^a-zA-Z0-9_-]|UndefValue::get)' 'HEAD~1' HEAD
clang/lib/CodeGen/TargetBu
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Jonathan Thackray (jthackray)
Changes
As mentioned in
https://discourse.llvm.org/t/rfc-rename-source-files-in-clang-lib-codegen-targetbuiltins/87462/
it appears that MacOS's libtool warns about source filenames that are
identically named
https://github.com/jthackray created
https://github.com/llvm/llvm-project/pull/150054
As mentioned in
https://discourse.llvm.org/t/rfc-rename-source-files-in-clang-lib-codegen-targetbuiltins/87462/
it appears that MacOS's libtool warns about source filenames that are
identically named, even i
OCHyams wrote:
/cherry-pick bbe912f1e74252f1f57b5d6c6d97a418947f4aa0
https://github.com/llvm/llvm-project/pull/149076
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/OCHyams milestoned
https://github.com/llvm/llvm-project/pull/149076
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/OCHyams closed
https://github.com/llvm/llvm-project/pull/149076
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Orlando Cazalet-Hyams
Date: 2025-07-22T17:19:58+01:00
New Revision: bbe912f1e74252f1f57b5d6c6d97a418947f4aa0
URL:
https://github.com/llvm/llvm-project/commit/bbe912f1e74252f1f57b5d6c6d97a418947f4aa0
DIFF:
https://github.com/llvm/llvm-project/commit/bbe912f1e74252f1f57b5d6c6d97a418947f4a
@@ -710,17 +704,25 @@ static bool forEachDriverJob(
static bool createAndRunToolInvocation(
std::vector CommandLine, DependencyScanningAction &Action,
-FileManager &FM,
+IntrusiveRefCntPtr FS,
std::shared_ptr &PCHContainerOps,
DiagnosticsEngine &Diags, De
github-actions[bot] wrote:
@sivadeilra 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 bui
Author: sivadeilra
Date: 2025-07-22T09:18:13-07:00
New Revision: b933f0c376c983614a0701f3bfd4054cf8fe4386
URL:
https://github.com/llvm/llvm-project/commit/b933f0c376c983614a0701f3bfd4054cf8fe4386
DIFF:
https://github.com/llvm/llvm-project/commit/b933f0c376c983614a0701f3bfd4054cf8fe4386.diff
LO
https://github.com/dpaoliello closed
https://github.com/llvm/llvm-project/pull/144745
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-with-thin-lto-ubuntu` running on `as-worker-92` while building `clang`
at step 6 "build-stage1-compiler".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/127/builds/4165
Here is the relevant pi
jmorse wrote:
Seems like a fair choice to me, and we can refine it in the future; ship it!
https://github.com/llvm/llvm-project/pull/149076
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-comm
https://github.com/jansvoboda11 edited
https://github.com/llvm/llvm-project/pull/149904
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
OCHyams wrote:
> LGTM -- is there a possibility that there'll be multiple stores coming from
> (output arguments of?) inline asm blocks? One wonders what the desired
> stepping behaviour is then: arguably you want to step through all the
> side-effects, or some might want to just consider the
https://github.com/jmorse approved this pull request.
LGTM -- is there a possibility that there'll be multiple stores coming from
(output arguments of?) inline asm blocks? One wonders what the desired stepping
behaviour is then: arguably you want to step through all the side-effects, or
some m
bd1976bris wrote:
FYI: @jmagee, @kbelochapka, @romanova-ekaterina, @playstation-edd, @nga888
https://github.com/llvm/llvm-project/pull/149988
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-co
abhishek-kaushik22 wrote:
@topperc can you please review since you've review similar commits in the past?
https://github.com/llvm/llvm-project/pull/150044
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/li
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Abhishek Kaushik (abhishek-kaushik22)
Changes
Fixes #149866
---
Full diff: https://github.com/llvm/llvm-project/pull/150044.diff
2 Files Affected:
- (modified) clang/lib/CodeGen/CGCall.cpp (+5-3)
- (added) clang/test/CodeGen/target-fea
https://github.com/abhishek-kaushik22 created
https://github.com/llvm/llvm-project/pull/150044
Fixes #149866
>From 480f5521ff5f0767ea295ef61a054f35961be3b0 Mon Sep 17 00:00:00 2001
From: Abhishek Kaushik
Date: Tue, 22 Jul 2025 21:03:17 +0530
Subject: [PATCH] [Clang]Throw frontend error for tar
DKLoehr wrote:
> GlobPattern is also used in binary utilities' symbol/section name matching
> where we want to be rigid
Thanks for pointing that out! I narrowed the scope of the change so that the
parts of the code which want it have to explicitly enable it. Right now that's
just the special
https://github.com/bjosv updated
https://github.com/llvm/llvm-project/pull/149790
From c0b8835f8aeebe6523c88b32163fbe6c77d9ce83 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Svensson?=
Date: Thu, 17 Jul 2025 12:14:48 +0200
Subject: [PATCH 1/4] Add C23 tests for bugprone-signed-char-misu
bjosv wrote:
> what about enum with unsigned underlying type. it looks not covered by tests
I added a test for enums with unsigned underlying type.
I also added additional cases that should be ignored by the check, similar to
what exists for C++.
https://github.com/llvm/llvm-project/pull/14979
https://github.com/bjosv updated
https://github.com/llvm/llvm-project/pull/149790
From c0b8835f8aeebe6523c88b32163fbe6c77d9ce83 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Svensson?=
Date: Thu, 17 Jul 2025 12:14:48 +0200
Subject: [PATCH 1/4] Add C23 tests for bugprone-signed-char-misu
1 - 100 of 297 matches
Mail list logo
