@@ -359,6 +356,176 @@ struct TemplateParameterListBuilder {
return Builder;
}
};
+
+// Builder for methods of builtin types. Allows adding methods to builtin types
+// using the builder pattern like this:
+//
+// BuiltinTypeMethodBuilder(Sema, RecordBuilder, "MethodName
dkolsen-pgi wrote:
> Does https://mlir.llvm.org/docs/Dialects/Builtin/#fusedloc suit the situation
> [of recording locations of macro expansions]?
Maybe? Right now I think `FusedLoc` is used by ClangIR to represent a source
range. Maybe it also could be used for macro expansion locations. I
@@ -122,7 +122,6 @@ class SpecialCaseList {
// Returns zero if no match is found.
unsigned match(StringRef Query) const;
- private:
StringMap> Globs;
AaronBallman wrote:
This can be made protected at least though, right?
https://github.com/llvm
erichkeane wrote:
> > Does https://mlir.llvm.org/docs/Dialects/Builtin/#fusedloc suit the
> > situation [of recording locations of macro expansions]?
>
> Maybe? Right now I think `FusedLoc` is used by ClangIR to represent a source
> range. Maybe it also could be used for macro expansion locati
@@ -831,6 +831,28 @@ ASTContext::getCanonicalTemplateTemplateParmDecl(
return CanonTTP;
}
+/// Check if a type can have its sanitizer instrumentation elided.
+/// Determine this by its presence in a SCL alongside its specified categories.
+/// For example:
+/// ignorelist.tx
https://github.com/wlei-llvm updated
https://github.com/llvm/llvm-project/pull/114364
>From a7b444bd75d6f83ed0f5692783990a59f36e8459 Mon Sep 17 00:00:00 2001
From: wlei
Date: Thu, 31 Oct 2024 09:58:27 -0700
Subject: [PATCH 1/4] Reapply "[InstrPGO] Support cold function coverage
instrumentation
@@ -24,9 +27,140 @@ CIRGenModule::CIRGenModule(mlir::MLIRContext &context,
clang::ASTContext &astctx,
const clang::CodeGenOptions &cgo,
DiagnosticsEngine &diags)
-: astCtx(astctx), langOpts(ast
jhuber6 wrote:
> > Can this be done through `-Xoffload-linker`?
>
> No. I tried several different things, but was not able to get the right
> command line option passed to lld (in the
> clang->clang-linker-wrapper->clang->lld chain).
This works for me,
```console
$ clang input.c -fopenmp --of
https://github.com/sarnex created
https://github.com/llvm/llvm-project/pull/114488
This fixes the current sanitizer CI failures. I manually confirmed the fix with
a MemorySanitizer build.
>From 51227ad50bff12eff5a4f835686f13d2444848ea Mon Sep 17 00:00:00 2001
From: "Sarnie, Nick"
Date: Thu, 3
https://github.com/wlei-llvm updated
https://github.com/llvm/llvm-project/pull/114364
>From a7b444bd75d6f83ed0f5692783990a59f36e8459 Mon Sep 17 00:00:00 2001
From: wlei
Date: Thu, 31 Oct 2024 09:58:27 -0700
Subject: [PATCH 1/4] Reapply "[InstrPGO] Support cold function coverage
instrumentation
@@ -3437,10 +3437,10 @@ bool Sema::SubstDefaultArgument(
// template void f(T a, int = decltype(a)());
// void g() { f(0); }
LIS = std::make_unique(*this);
- FunctionDecl *PatternFD = FD->getTemplateInstantiationPattern(
- /*ForDefinition*/ f
@@ -585,10 +585,11 @@ Bug Fixes to C++ Support
- Clang incorrectly considered a class with an anonymous union member to not be
const-default-constructible even if a union member has a default member
initializer.
(#GH95854).
-- Fixed an assertion failure when evaluating an
jhuber6 wrote:
> The toothpaste is out of the tube once the IR is produced. If some toolchain
> were relying on the global target machine features, there are opportunities
> for error on each tool invocation. The absence of the attribute does not tell
> you what the final compilation context w
@@ -21,6 +21,22 @@
// CHECK-NO-PIE-NOT: "-pie"
// CHECK-SHARED: "--shared"
+// Test the driver supplies an --image-base to the linker only for non-pie
+// executables.
+
+// RUN: %clang --target=x86_64-sie-ps5 -static %s -### 2>&1 | FileCheck
--check-prefixes=CHECK-BASE %s
+/
@@ -295,6 +302,9 @@ void tools::PS5cpu::Linker::ConstructJob(Compilation &C,
const JobAction &JA,
if (Shared)
CmdArgs.push_back("--shared");
+ if (!Relocatable && !Shared && !PIE)
pogo59 wrote:
Does this want to consider `Static` as well? Just wonderi
https://github.com/a-tarasyuk updated
https://github.com/llvm/llvm-project/pull/113777
>From 78019b9d9dc138f38bb5b32576b621351ae6427c Mon Sep 17 00:00:00 2001
From: Oleksandr T
Date: Sun, 27 Oct 2024 01:07:57 +0300
Subject: [PATCH] [Clang] prevent assertion failure from an invalid template
ins
Author: Chuanqi Xu
Date: 2024-10-31T15:52:18+08:00
New Revision: d5cdc26f555918e6f292f16ac3800afc97093aac
URL:
https://github.com/llvm/llvm-project/commit/d5cdc26f555918e6f292f16ac3800afc97093aac
DIFF:
https://github.com/llvm/llvm-project/commit/d5cdc26f555918e6f292f16ac3800afc97093aac.diff
LO
https://github.com/rampitec updated
https://github.com/llvm/llvm-project/pull/113610
>From edda0e600abeabff4d44e8b0b897104efacc8f98 Mon Sep 17 00:00:00 2001
From: Stanislav Mekhanoshin
Date: Thu, 24 Oct 2024 11:31:52 -0700
Subject: [PATCH 1/2] [AMDGPU] Allow overload of __builtin_amdgcn_mov_dpp
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lld-x86_64-win` running on
`as-worker-93` while building `clang,llvm` at step 7
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/146/builds/1492
Here is the releva
@@ -10,3 +10,7 @@ int test_cmpccxadd32(void *__A, int __B, int __C) {
long long test_cmpccxadd64(void *__A, long long __B, long long __C) {
return _cmpccxadd_epi64(__A, __B, __C, 16); // expected-error {{argument
value 16 is outside the valid range [0, 15]}}
}
+
+long long t
https://github.com/5chmidti updated
https://github.com/llvm/llvm-project/pull/113833
>From 99090f44fdfe049d7e01e469787ebb0039b965c4 Mon Sep 17 00:00:00 2001
From: Julian Schmidt
Date: Sun, 27 Oct 2024 20:47:21 +0100
Subject: [PATCH 1/3] [clang-tidy] fix crash in
altera-id-dependent-backward-br
Author: Timm Baeder
Date: 2024-10-31T10:59:53+01:00
New Revision: ccb7cc319f8ea07bb64c2efb0c4f1e42076ef446
URL:
https://github.com/llvm/llvm-project/commit/ccb7cc319f8ea07bb64c2efb0c4f1e42076ef446
DIFF:
https://github.com/llvm/llvm-project/commit/ccb7cc319f8ea07bb64c2efb0c4f1e42076ef446.diff
L
https://github.com/tbaederr closed
https://github.com/llvm/llvm-project/pull/114380
___
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` at step 5 "ninja
check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/65/builds/6967
Here is the relevant piec
@@ -24,12 +24,12 @@ the spirit in which it's intended - a guide to make it
easier to communicate
and participate in the community.
This code of conduct applies to all spaces managed by the LLVM project or The
-LLVM Foundation. This includes IRC channels, mailing lists, bug tr
https://github.com/kbeyls commented:
Overall looks great, thank you :)
I've left one nit-picky comment on keeping IRC mentioned in the code of conduct
page, as even though it's a "legacy" communication channel, it continues to
exist, so the code-of-conduct continues to apply there.
https://git
https://github.com/kbeyls edited
https://github.com/llvm/llvm-project/pull/114276
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/FreddyLeaf updated
https://github.com/llvm/llvm-project/pull/114367
>From 4c0a5729c8da644cfc01ad25820386f0cc289316 Mon Sep 17 00:00:00 2001
From: Freddy Ye
Date: Fri, 25 Oct 2024 10:00:16 +0800
Subject: [PATCH 1/2] [X86][CFE] Correct parameter type of _cmpccxadd_epi64
---
c
@@ -10,3 +10,7 @@ int test_cmpccxadd32(void *__A, int __B, int __C) {
long long test_cmpccxadd64(void *__A, long long __B, long long __C) {
return _cmpccxadd_epi64(__A, __B, __C, 16); // expected-error {{argument
value 16 is outside the valid range [0, 15]}}
}
+
+long long t
https://github.com/phoebewang approved this pull request.
LGTM, thanks!
https://github.com/llvm/llvm-project/pull/114367
___
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 `premerge-monolithic-linux`
running on `premerge-linux-1` while building `clang` at step 7
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/153/builds/13261
Here is
Author: Julian Schmidt
Date: 2024-10-31T09:13:51+01:00
New Revision: a776bd1a92126bf9bd1b51511364194fd75aa606
URL:
https://github.com/llvm/llvm-project/commit/a776bd1a92126bf9bd1b51511364194fd75aa606
DIFF:
https://github.com/llvm/llvm-project/commit/a776bd1a92126bf9bd1b51511364194fd75aa606.diff
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-ppc64le-rhel`
running on `ppc64le-clang-rhel-test` while building `clang` at step 7
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/145/builds/2841
Here is
https://github.com/tbaederr created
https://github.com/llvm/llvm-project/pull/114380
We have a special diagnostic ID for this.
>From e172eea48fb60282ded94f7e4e61f4cf60a289ec Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Timm=20B=C3=A4der?=
Date: Thu, 31 Oct 2024 10:29:48 +0100
Subject: [PATCH] [cla
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Timm Baeder (tbaederr)
Changes
We have a special diagnostic ID for this.
---
Full diff: https://github.com/llvm/llvm-project/pull/114380.diff
2 Files Affected:
- (modified) clang/lib/AST/ByteCode/Interp.h (+8-2)
- (modified) clang/test
https://github.com/ChuanqiXu9 created
https://github.com/llvm/llvm-project/pull/114382
According to our previous consensus in
https://clang.llvm.org/docs/StandardCPlusPlusModules.html#reduced-bmi, the
reduced BMI will be the default and recommend users to use the new option.
The `-fexperiment
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-aarch64-global-isel`
running on `linaro-clang-aarch64-global-isel` while building `clang` at step 7
"ninja check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/125/builds/3168
Here is the
Author: Timm Baeder
Date: 2024-10-31T10:13:40+01:00
New Revision: f0b9a0ba0649e11f190d20e86f92b566dfb8da0f
URL:
https://github.com/llvm/llvm-project/commit/f0b9a0ba0649e11f190d20e86f92b566dfb8da0f
DIFF:
https://github.com/llvm/llvm-project/commit/f0b9a0ba0649e11f190d20e86f92b566dfb8da0f.diff
L
Author: Stanislav Mekhanoshin
Date: 2024-10-31T02:19:20-07:00
New Revision: ba1a09da8d4d8138e932d3b6dc96a7bfc5b86fe7
URL:
https://github.com/llvm/llvm-project/commit/ba1a09da8d4d8138e932d3b6dc96a7bfc5b86fe7
DIFF:
https://github.com/llvm/llvm-project/commit/ba1a09da8d4d8138e932d3b6dc96a7bfc5b86f
https://github.com/rampitec closed
https://github.com/llvm/llvm-project/pull/113610
___
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
`sanitizer-x86_64-linux-fast` running on `sanitizer-buildbot3` while building
`clang` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/169/builds/4819
Here is the relevant piece o
@@ -1562,7 +1562,9 @@ unsigned
LoongArchAsmParser::checkTargetMatchPredicate(MCInst &Inst) {
unsigned Opc = Inst.getOpcode();
switch (Opc) {
default:
-if (Opc >= LoongArch::AMADD_D && Opc <= LoongArch::AMXOR_W) {
+// amcas[_db].{b/h/w/d} didn't need this judgemen
https://github.com/xen0n commented:
I think this is getting more convoluted than necessary? For example, I didn't
see a `setOperationAction(ISD::ATOMIC_CMP_SWAP, Legal)` call gated on presence
of the `lamcas` feature, which I think would render a lot (if not most) of the
changes here made to t
@@ -363,6 +363,10 @@ LoongArchTargetLowering::LoongArchTargetLowering(const
TargetMachine &TM,
setPrefFunctionAlignment(Subtarget.getPrefFunctionAlignment());
setPrefLoopAlignment(Subtarget.getPrefLoopAlignment());
setMaxBytesForAlignment(Subtarget.getMaxBytesForAlignmen
https://github.com/xen0n edited https://github.com/llvm/llvm-project/pull/114189
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,30 @@
+/// Test -m[no]lamcas options.
+
+// RUN: %clang --target=loongarch64 -mlamcas -fsyntax-only %s -### 2>&1 | \
+// RUN: FileCheck %s --check-prefix=CC1-LAMCAS
+// RUN: %clang --target=loongarch64 -mno-lamcas -fsyntax-only %s -### 2>&1 | \
+// RUN: FileChec
@@ -1182,8 +1187,13 @@
PassBuilder::buildModuleSimplificationPipeline(OptimizationLevel Level,
const bool IsCtxProfUse =
!UseCtxProfile.empty() && Phase == ThinOrFullLTOPhase::ThinLTOPreLink;
+ // Enable cold function coverage instrumentation if
+ // InstrumentColdF
Author: Dmitry Chernenkov
Date: 2024-10-31T10:55:17Z
New Revision: d924a9ba03a05b417676e84f6c81aac44f907f71
URL:
https://github.com/llvm/llvm-project/commit/d924a9ba03a05b417676e84f6c81aac44f907f71
DIFF:
https://github.com/llvm/llvm-project/commit/d924a9ba03a05b417676e84f6c81aac44f907f71.diff
Author: Dmitry Chernenkov
Date: 2024-10-31T10:55:17Z
New Revision: 06e28ed84f3f0a05b493699965e18e7a5aeaccd2
URL:
https://github.com/llvm/llvm-project/commit/06e28ed84f3f0a05b493699965e18e7a5aeaccd2
DIFF:
https://github.com/llvm/llvm-project/commit/06e28ed84f3f0a05b493699965e18e7a5aeaccd2.diff
@@ -0,0 +1,13 @@
+// This test checks if Window PE file compiled with -flto option contains a
magic
+// string "LTCG" to indicate LTO compilation.
+
+// REQUIRES: system-windows
+
+// RUN: %clang --target=x86_64-pc-windows-msvc -flto -fuse-ld=lld %s -o %t.exe
+// RUN: dumpbin /H
Author: Simon Pilgrim
Date: 2024-10-31T11:50:19Z
New Revision: fcaa8c6e2240a950d3d86fb723d9b0a363b7346a
URL:
https://github.com/llvm/llvm-project/commit/fcaa8c6e2240a950d3d86fb723d9b0a363b7346a
DIFF:
https://github.com/llvm/llvm-project/commit/fcaa8c6e2240a950d3d86fb723d9b0a363b7346a.diff
LOG:
Timm =?utf-8?q?Bäder?= ,
Timm =?utf-8?q?Bäder?= ,
Timm =?utf-8?q?Bäder?= ,
Timm =?utf-8?q?Bäder?=
Message-ID:
In-Reply-To:
https://github.com/AaronBallman edited
https://github.com/llvm/llvm-project/pull/112126
___
cfe-commits mailing list
cfe-commit
aganea wrote:
I am just curious what is the purpose of this? Is it just for feature parity?
Can you also investigate if MSVC emits other special things/sections in the
binary in LTCG/PGO builds?
https://github.com/llvm/llvm-project/pull/114260
___
cf
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Jannick Kremer (DeinAlptraum)
Changes
This removes workarounds for Python versions before 3.6, since our minimum
Python version has been bumped to 3.8
---
Full diff: https://github.com/llvm/llvm-project/pull/114399.diff
4 Files Affected
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`sanitizer-x86_64-linux-bootstrap-asan` running on `sanitizer-buildbot1` while
building `clang` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/52/builds/3353
Here is the relevan
https://github.com/kbeyls approved this pull request.
https://github.com/llvm/llvm-project/pull/114276
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Timm =?utf-8?q?Bäder?= ,
Timm =?utf-8?q?Bäder?= ,
Timm =?utf-8?q?Bäder?= ,
Timm =?utf-8?q?Bäder?=
Message-ID:
In-Reply-To:
@@ -0,0 +1,399 @@
+// RUN: %clang_cc1 -verify=ref,both -std=c++2a -fsyntax-only %s
+// RUN: %clang_cc1 -verify=ref,both -std=c++2a -fsyntax-only -triple
a
https://github.com/Endilll approved this pull request.
https://github.com/llvm/llvm-project/pull/114399
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/Endilll approved this pull request.
https://github.com/llvm/llvm-project/pull/114397
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tbaederr created
https://github.com/llvm/llvm-project/pull/114400
When we see an array root, that pointer might yet again be an array element, so
check for that.
>From 2820aff9d4fae148d04ff6b975269df3039a92f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Timm=20B=C3=A4der?=
Date
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Timm Baeder (tbaederr)
Changes
When we see an array root, that pointer might yet again be an array element, so
check for that.
---
Full diff: https://github.com/llvm/llvm-project/pull/114400.diff
3 Files Affected:
- (modified) clang/li
https://github.com/bob80905 updated
https://github.com/llvm/llvm-project/pull/113730
>From a31199224c19c1087b114de29d864125b720e6d8 Mon Sep 17 00:00:00 2001
From: Joshua Batista
Date: Fri, 25 Oct 2024 12:33:05 -0700
Subject: [PATCH 1/5] add type trait
---
.../clang/AST/CXXRecordDeclDefinition
https://github.com/rniwa updated
https://github.com/llvm/llvm-project/pull/114374
>From 474490de53c029ab59008bed9fc33f61db4cb1d7 Mon Sep 17 00:00:00 2001
From: Ryosuke Niwa
Date: Thu, 31 Oct 2024 01:12:35 -0700
Subject: [PATCH 1/2] [webkit.UncountedLambdaCapturesChecker] Ignore trivial
functio
@@ -0,0 +1,342 @@
+// RUN: %clang_analyze_cc1
-analyzer-checker=alpha.webkit.UncheckedLocalVarsChecker -verify %s
+
+#include "mock-types.h"
+#include "mock-system-header.h"
+
+void someFunction();
+
+namespace raw_ptr {
+void foo() {
+ CheckedObj *bar;
+ // FIXME: later on we
https://github.com/erichkeane edited
https://github.com/llvm/llvm-project/pull/113483
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
macurtis-amd wrote:
> > > Can this be done through `-Xoffload-linker`?
> >
> >
> > No. I tried several different things, but was not able to get the right
> > command line option passed to lld (in the
> > clang->clang-linker-wrapper->clang->lld chain).
>
> This works for me,
>
> ```
> $ cla
macurtis-amd wrote:
> Can this be done through `-Xoffload-linker`?
No. I tried several different things, but was not able to get the right command
line option passed to lld (in the clang->clang-linker-wrapper->clang->lld
chain).
https://github.com/llvm/llvm-project/pull/114401
___
https://github.com/cyndyishida approved this pull request.
I initially touched this code because I needed to be able to map back input
headers from a destination location (DSTROOT) to where they were resolved with
headermaps (SRCROOT) for `tapi`/`clang-installapi`. But looking at the code it
o
@@ -10,4 +10,57 @@
//
//===--===//
-#include
+#include "clang/CIR/Dialect/IR/CIRDialect.h"
+
+#include "mlir/Support/LogicalResult.h"
+
+#include "clang/CIR/Dialect/IR/CIROpsDialect.cpp.inc"
https://github.com/dkolsen-pgi updated
https://github.com/llvm/llvm-project/pull/113483
>From fd38921f9899e3e5ae538a94f123433119919731 Mon Sep 17 00:00:00 2001
From: David Olsen
Date: Wed, 23 Oct 2024 11:01:40 -0700
Subject: [PATCH 1/3] [CIR] Call code gen; create empty cir.func op
Finish hook
https://github.com/AlexVlx edited
https://github.com/llvm/llvm-project/pull/114481
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -13,4 +13,22 @@
#ifndef LLVM_CLANG_CIR_DIALECT_IR_CIRDIALECT_H
#define LLVM_CLANG_CIR_DIALECT_IR_CIRDIALECT_H
+#include "mlir/IR/Builders.h"
dkolsen-pgi wrote:
`git clang-format` will alphabetize a block of includes that are not separated
by blank lines.
@@ -13,4 +13,22 @@
#ifndef LLVM_CLANG_CIR_DIALECT_IR_CIRDIALECT_H
#define LLVM_CLANG_CIR_DIALECT_IR_CIRDIALECT_H
+#include "mlir/IR/Builders.h"
+#include "mlir/IR/BuiltinOps.h"
+#include "mlir/IR/BuiltinTypes.h"
+#include "mlir/IR/Dialect.h"
+#include "mlir/IR/OpDefinition.h"
bwendling wrote:
This is a new PR, because GitHub messed up. Here's the original:
https://github.com/llvm/llvm-project/pull/102549
https://github.com/llvm/llvm-project/pull/114495
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.l
asudarsa wrote:
Sanitizer test failures should be resolved by
https://github.com/llvm/llvm-project/pull/114488 (under review).
Thanks to @sarnex for the timely fix.
Sincerely
https://github.com/llvm/llvm-project/pull/112245
___
cfe-commits mailing li
asudarsa wrote:
This is not the correct fix. Closing it.
Thanks
https://github.com/llvm/llvm-project/pull/114434
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/asudarsa closed
https://github.com/llvm/llvm-project/pull/114434
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
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 51a4f319f022b99f231e52fab97de28b6f1db591
a5245e5d6e026f389e64245a8ce4df643abec4a5 --e
https://github.com/jhuber6 approved this pull request.
Good catch, thanks.
https://github.com/llvm/llvm-project/pull/114488
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/owenca created
https://github.com/llvm/llvm-project/pull/114506
Fixes #114408.
>From 4702c777252678bf3633fd72a0470d135a54c4ba Mon Sep 17 00:00:00 2001
From: Owen Pan
Date: Thu, 31 Oct 2024 21:40:17 -0700
Subject: [PATCH] [clang-format] Fix a regression in parsing `switch` in
llvmbot wrote:
@llvm/pr-subscribers-clang-format
Author: Owen Pan (owenca)
Changes
Fixes #114408.
---
Full diff: https://github.com/llvm/llvm-project/pull/114506.diff
2 Files Affected:
- (modified) clang/lib/Format/UnwrappedLineParser.cpp (+6-2)
- (modified) clang/unittests/Format/Tok
boomanaiden154 wrote:
> can we have clang-format-style-options rebuilt only when it's outdated, i.e.
> only if at least one of the following has been updated?
We can, but it requires more changes that I'm not sure are worth doing given
that this step takes essentially zero time compared to reg
owenca wrote:
@boomanaiden154 can we have `clang-format-style-options` rebuilt only when it's
outdated, i.e. only if at least one of the following has been updated?
```
clang/include/clang/Format/Format.h
clang/include/clang/Tooling/Inclusions/IncludeStyle.h
clang/docs/ClangFormatStyleOptions.rs
https://github.com/t-rasmud approved this pull request.
LGTM!
https://github.com/llvm/llvm-project/pull/113708
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
rniwa wrote:
> LGTM!
Thanks for the review!
https://github.com/llvm/llvm-project/pull/113708
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/rniwa updated
https://github.com/llvm/llvm-project/pull/113708
>From cf5ca301bc9ed2c65eed92e7299bf598d5f88103 Mon Sep 17 00:00:00 2001
From: Ryosuke Niwa
Date: Sat, 14 Sep 2024 01:46:23 -0700
Subject: [PATCH 1/2] Introduce a new WebKit checker for a unchecked local
variable
@@ -2238,7 +2238,10 @@ prepareCallHierarchy(ParsedAST &AST, Position Pos,
PathRef TUPath) {
for (const NamedDecl *Decl : getDeclAtPosition(AST, *Loc, {})) {
if (!(isa(Decl) &&
cast(Decl)->isFunctionOrMethod()) &&
-Decl->getKind() != Decl::Kind::Function
https://github.com/HighCommander4 edited
https://github.com/llvm/llvm-project/pull/113900
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/HighCommander4 requested changes to this pull request.
Thanks for the patch!
https://github.com/llvm/llvm-project/pull/113900
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Xi Ruoyao (xry111)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/114509.diff
2 Files Affected:
- (added) clang/test/Headers/lasxintrin.c (+6)
- (added) clang/test/Headers/lsxintrin.c (+6)
``diff
diff --gi
https://github.com/xry111 created
https://github.com/llvm/llvm-project/pull/114509
None
>From 1bbbc1c38715f42e6014ee319d76af9a4015e4d5 Mon Sep 17 00:00:00 2001
From: Xi Ruoyao
Date: Fri, 1 Nov 2024 00:00:14 +0800
Subject: [PATCH] [LoongArch][Clang] Add tests for #110834
---
clang/test/Header
https://github.com/xry111 created
https://github.com/llvm/llvm-project/pull/114512
The lsxintrin.h and and lasxintrin.h headers uses `signed char` vectors
instead of `unsigned char` vectors. GCC also uses `signed char` for
them, so align their definition with the headers and GCC.
Depends on #1
https://github.com/xry111 created
https://github.com/llvm/llvm-project/pull/114511
These builtins operate on int8 vectors, not int16 vectors. So the old
definition does not make any sense.
Depends on #114510. Part of #110834 fix.
>From 1bbbc1c38715f42e6014ee319d76af9a4015e4d5 Mon Sep 17 00:0
llvmbot wrote:
@llvm/pr-subscribers-backend-loongarch
Author: Xi Ruoyao (xry111)
Changes
These builtins operate on int8 vectors, not int16 vectors. So the old
definition does not make any sense.
Depends on #114510. Part of #110834 fix.
---
Patch is 58.14 KiB, truncated to 20.00 KiB be
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Xi Ruoyao (xry111)
Changes
These builtins operate on int8 vectors, not int16 vectors. So the old
definition does not make any sense.
Depends on #114510. Part of #110834 fix.
---
Patch is 58.14 KiB, truncated to 20.00 KiB below, full ve
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Xi Ruoyao (xry111)
Changes
`-flax-vector-conversions=none` does not allow an implicit conversion
from `signed char` vector to `char` vector, and we cannot remove `signed`
from `v16i8` or `v32i8` because doing so will break our expectation w
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Xi Ruoyao (xry111)
Changes
The lsxintrin.h and and lasxintrin.h headers uses `unsigned char`
vectors instead of `signed char` vectors. GCC also uses `unsigned char`
for them, so align their definition with the headers and GCC.
Fixes #
https://github.com/xry111 created
https://github.com/llvm/llvm-project/pull/114514
All other bitwise vector builtins use `unsigned char` vector operands,
so it does not make too much sense to use `signed char` for the orn
operation alone.
The same change has been also proposed for GCC:
http
llvmbot wrote:
@llvm/pr-subscribers-backend-loongarch
@llvm/pr-subscribers-backend-x86
Author: Xi Ruoyao (xry111)
Changes
All other bitwise vector builtins use `unsigned char` vector operands,
so it does not make too much sense to use `signed char` for the orn
operation alone.
The sam
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Xi Ruoyao (xry111)
Changes
The lsxintrin.h and and lasxintrin.h headers uses `signed char` vectors
instead of `unsigned char` vectors. GCC also uses `signed char` for
them, so align their definition with the headers and GCC.
Depends on #1
401 - 500 of 565 matches
Mail list logo
