https://github.com/yuxuanchen1997 updated
https://github.com/llvm/llvm-project/pull/94693
>From 4e4bcdc19268543a8348736dede46d8f8cad0066 Mon Sep 17 00:00:00 2001
From: Yuxuan Chen
Date: Tue, 4 Jun 2024 23:22:00 -0700
Subject: [PATCH 1/3] [Clang] Introduce [[clang::coro_inplace_task]]
---
clan
https://github.com/yuxuanchen1997 updated
https://github.com/llvm/llvm-project/pull/94693
>From 4e4bcdc19268543a8348736dede46d8f8cad0066 Mon Sep 17 00:00:00 2001
From: Yuxuan Chen
Date: Tue, 4 Jun 2024 23:22:00 -0700
Subject: [PATCH 1/3] [Clang] Introduce [[clang::coro_inplace_task]]
---
clan
@@ -1,9 +1,10 @@
// RUN: %clang_cc1 -triple dxil-pc-shadermodel6.3-library -x hlsl -o -
-fsyntax-only %s -verify
-// expected-error@+1 {{invalid resource class specifier 'c' used; expected
'b', 's', 't', or 'u'}}
-float a : register(c0, space1);
+// valid, The register keywor
sdkrystian wrote:
@pranavk see #98613
https://github.com/llvm/llvm-project/pull/98547
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
mizvekov wrote:
> Clarifying a couple of things here
I think we need the distinction between simple NFC, for trivial,
non-controversial and non-surprising changes like some renames, small
whitespace / formatting change, documentation changes, and complex NFC, which
requires some thinking and
https://github.com/vfdff created https://github.com/llvm/llvm-project/pull/98704
Check whether timeout exists in the Windows operating system.
>From 1b8503202474c15aa46fc4cc9151003a8d3ca336 Mon Sep 17 00:00:00 2001
From: zhongyunde 00443407
Date: Fri, 12 Jul 2024 21:09:46 -0400
Subject: [PATCH]
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Allen (vfdff)
Changes
Check whether timeout exists in the Windows operating system.
---
Full diff: https://github.com/llvm/llvm-project/pull/98704.diff
1 Files Affected:
- (added) clang/test/CodeGen/math-libcalls-tbaa.cpp (+38)
`
phoebewang wrote:
> > max aligment [...] LLVM Verifier accepts is 2^14
>
> The verifier limit in most places is 2^32. It looks like 2^14 is specifically
> for ByVal. And there isn't really any good reason for that limit; it was
> arbitrarily chosen in
> [66011c1](https://github.com/llvm/llvm-
@@ -133,6 +133,7 @@ struct TransferrableTargetInfo {
unsigned short SuitableAlign;
unsigned short NewAlign;
unsigned MaxVectorAlign;
phoebewang wrote:
What's this used for? Can we limit it to 2^14?
https://github.com/llvm/llvm-project/pull/98629
___
pranavk wrote:
This doesn't seem to handle all the cases? See
https://github.com/abseil/abseil-cpp/pull/1711 for absl build failures that are
not silenced by using this option.
https://github.com/llvm/llvm-project/pull/98613
___
cfe-commits mailing l
vfdff wrote:
hi @efriedma-quic I find the case will timeout even without this changes ,so
would it reasonable to add **require Linux for this test** now ?
https://buildkite.com/llvm-project/github-pull-requests/builds/80879#0190a9c3-b007-4daa-9656-0c8f00601ee9
https://github.com/llvm/llvm-p
vfdff wrote:
require Linux for this test as it time out on Windows ?
https://github.com/llvm/llvm-project/pull/98704
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/shafik approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/96228
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/shafik commented:
Thank you for this fix!
https://github.com/llvm/llvm-project/pull/98439
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
shafik wrote:
I don't think the build error is related to this change.
https://github.com/llvm/llvm-project/pull/98439
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
CoTinker wrote:
Inconsistency here is inevitable.
Such struct `SuperEmpty { struct{ int a[0];} b;}` in c++ mode can not be
ignored in i386 for that c++ fields are never empty, and its TypeInfo.Width =
TypeInfo.Align = 0.
https://github.com/llvm/llvm-project/blob/594989918bf9e178f3b7c5e200d700d0
shafik wrote:
> The sad part is that MSVC and some old versions of GCC don't like `template`
> being added here :(
It looks like the description provides a workaround for gcc but a bug report
against MSVC should be filed if we don' have one already.
https://github.com/llvm/llvm-project/pull/9
https://github.com/mizvekov approved this pull request.
LGTM.
If it does fix the mentioned issue, please add a release note.
https://github.com/llvm/llvm-project/pull/98699
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org
https://github.com/mizvekov approved this pull request.
LGTM, I agree that we currently don't use it, so we might as well remove it.
But the overall situation is all wrong, we shouldn't be storing fully formed
diagnostic strings in the AST, we should be storing them as PartialDiagnostics.
But
Author: Younan Zhang
Date: 2024-07-13T11:49:21+08:00
New Revision: fb19649535d3d31a748409542947d09291643204
URL:
https://github.com/llvm/llvm-project/commit/fb19649535d3d31a748409542947d09291643204
DIFF:
https://github.com/llvm/llvm-project/commit/fb19649535d3d31a748409542947d09291643204.diff
https://github.com/zyn0217 closed
https://github.com/llvm/llvm-project/pull/98654
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -7416,10 +7416,11 @@ NamedDecl *Sema::ActOnVariableDeclarator(
tryToFixVariablyModifiedVarType(TInfo, R, D.getIdentifierLoc(),
/*DiagID=*/0);
- if (const AutoType *AutoT = R->getAs())
-CheckConstrainedAuto(
-AutoT,
-
@@ -7416,10 +7416,11 @@ NamedDecl *Sema::ActOnVariableDeclarator(
tryToFixVariablyModifiedVarType(TInfo, R, D.getIdentifierLoc(),
/*DiagID=*/0);
- if (const AutoType *AutoT = R->getAs())
-CheckConstrainedAuto(
-AutoT,
-
https://github.com/androm3da created
https://github.com/llvm/llvm-project/pull/98712
These can be used to create a fully-bootstrapped toolchain to target hexagon
{baremetal,linux} with scripts like the ones in
https://github.com/quic/toolchain_for_hexagon
>From 3cb0ce53c66815496ac0b5296ee36aa
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Brian Cain (androm3da)
Changes
These can be used to create a fully-bootstrapped toolchain to target hexagon
{baremetal,linux} with scripts like the ones in
https://github.com/quic/toolchain_for_hexagon
---
Full diff: https://github.com/l
https://github.com/mizvekov requested changes to this pull request.
See previous comments, I think this is primarily an error recovery issue on the
decltype, we shouldn't let it escape an undeduced auto, as that would confuse
further analysis.
https://github.com/llvm/llvm-project/pull/98622
__
brad0 wrote:
> Hmm, this function also seems to exist on Linux, though. Additionally, from
> my `man syslog` docs:
I'm not sure what you mean by that in relation to this addition of a format
attribute.
> > The remaining arguments are a format, as in `printf(3)`, and any arguments
> > require
https://github.com/koachan created
https://github.com/llvm/llvm-project/pull/98713
Implement handling for `-m(no-)v8plus` flags to allow the user to switch
between V8 and V8+ mode with 32-bit code.
Currently it only toggles the V9 feature bit, ABI and codegen changes will be
done in future pa
llvmbot wrote:
@llvm/pr-subscribers-clang-driver
Author: Koakuma (koachan)
Changes
Implement handling for `-m(no-)v8plus` flags to allow the user to switch
between V8 and V8+ mode with 32-bit code.
Currently it only toggles the V9 feature bit, ABI and codegen changes will be
done in fut
Author: Timm Bäder
Date: 2024-07-13T07:25:47+02:00
New Revision: 7d5902025d20e00b1865d02dfe514fb35259ae2a
URL:
https://github.com/llvm/llvm-project/commit/7d5902025d20e00b1865d02dfe514fb35259ae2a
DIFF:
https://github.com/llvm/llvm-project/commit/7d5902025d20e00b1865d02dfe514fb35259ae2a.diff
LO
Author: Timm Bäder
Date: 2024-07-13T07:25:47+02:00
New Revision: 634128be4610a4d85d92935109ed7761f0e06af1
URL:
https://github.com/llvm/llvm-project/commit/634128be4610a4d85d92935109ed7761f0e06af1
DIFF:
https://github.com/llvm/llvm-project/commit/634128be4610a4d85d92935109ed7761f0e06af1.diff
LO
Author: Timm Bäder
Date: 2024-07-13T07:25:47+02:00
New Revision: 66e6df22b5a509c16e50364d72b1a40bacaea91a
URL:
https://github.com/llvm/llvm-project/commit/66e6df22b5a509c16e50364d72b1a40bacaea91a
DIFF:
https://github.com/llvm/llvm-project/commit/66e6df22b5a509c16e50364d72b1a40bacaea91a.diff
LO
efriedma-quic wrote:
The size of ArgFlagsTy is, as far as I can tell, basically irrelevant: it's
only used as part of computing the calling convention in isel. I don't think
anyone will notice if it's a few bytes larger.
The non-byval alignment limit was last adjusted in
https://reviews.llvm
@@ -133,6 +133,7 @@ struct TransferrableTargetInfo {
unsigned short SuitableAlign;
unsigned short NewAlign;
unsigned MaxVectorAlign;
efriedma-quic wrote:
It's used in the same ASTContext code that's modified by this patch. Probably
fine to adjust it fo
https://github.com/shafik requested changes to this pull request.
It looks like we are using the same pattern that fix is using in
`ASTStmtReader::VisitRequiresExpr` which gives me some comfort but I am not
happy that we have a relatively complex and easy to get wrong operation
repeated in thr
https://github.com/Lambdaris updated
https://github.com/llvm/llvm-project/pull/94137
>From 23669f721d056d6e4961e2572e438e5c1f91cab1 Mon Sep 17 00:00:00 2001
From: Lambdaris
Date: Sun, 2 Jun 2024 10:19:31 +0800
Subject: [PATCH 1/3] [coverage] Mark branches with either counter is zero as
folded
Lambdaris wrote:
Add an option "--mcdc-exclude" to control which conditions can be excluded from
coverage. By default it's "constant,unreachable".
https://github.com/llvm/llvm-project/pull/94137
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://github.com/Lambdaris updated
https://github.com/llvm/llvm-project/pull/94137
>From 23669f721d056d6e4961e2572e438e5c1f91cab1 Mon Sep 17 00:00:00 2001
From: Lambdaris
Date: Sun, 2 Jun 2024 10:19:31 +0800
Subject: [PATCH 1/3] [coverage] Mark branches with either counter is zero as
folded
Author: cor3ntin
Date: 2024-07-13T08:53:02+02:00
New Revision: 1fe406fffe11dad0457a4d214ce67bf492196145
URL:
https://github.com/llvm/llvm-project/commit/1fe406fffe11dad0457a4d214ce67bf492196145
DIFF:
https://github.com/llvm/llvm-project/commit/1fe406fffe11dad0457a4d214ce67bf492196145.diff
LOG:
https://github.com/cor3ntin closed
https://github.com/llvm/llvm-project/pull/95969
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
401 - 440 of 440 matches
Mail list logo
