mjklemm wrote:
@tblah Ping :-)
https://github.com/llvm/llvm-project/pull/90886
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
b-sumner wrote:
Looks good to me.
https://github.com/llvm/llvm-project/pull/85672
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/sdkrystian updated
https://github.com/llvm/llvm-project/pull/90760
>From e5e0f25de3307128914b6fcfc9223b389e7b6438 Mon Sep 17 00:00:00 2001
From: Krystian Stasiowski
Date: Wed, 1 May 2024 10:54:12 -0400
Subject: [PATCH 1/5] [Clang][Sema] Explicit template arguments are not
su
alexey-bataev wrote:
> > > > > ```llvm
> > > > > struct.anon
> > > > > ```
> > > >
> > > >
> > > > Can you provide full IR dump here?
> > >
> > >
> > > https://godbolt.org/z/48h5s3W6v
> >
> >
> > It does not look like the issue of the target code, I don't see any wrong
> > access for __con
https://github.com/sdkrystian closed
https://github.com/llvm/llvm-project/pull/81642
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/jhuber6 approved this pull request.
Hopefully in the future we can handle this in the linker better.
https://github.com/llvm/llvm-project/pull/85672
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-b
https://github.com/sdkrystian updated
https://github.com/llvm/llvm-project/pull/90760
>From e5e0f25de3307128914b6fcfc9223b389e7b6438 Mon Sep 17 00:00:00 2001
From: Krystian Stasiowski
Date: Wed, 1 May 2024 10:54:12 -0400
Subject: [PATCH 1/5] [Clang][Sema] Explicit template arguments are not
su
sdkrystian wrote:
This seems to cause a crash in lldb in
`ClassTemplateSpecializationDecl::getSourceRange()`... investigating
https://github.com/llvm/llvm-project/pull/81642
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.o
@@ -312,75 +300,76 @@ So all of the following name is not valid by default:
__test
// and so on ...
-If you still want to use the reserved module names for any reason, use
-``-Wno-reserved-module-identifier`` to suppress the warning.
+Using a reserved module name is st
Author: Edwin Vane
Date: 2024-05-07T21:06:51+02:00
New Revision: b1bc1dbea6d0423813bb73d625c6eedc040007ed
URL:
https://github.com/llvm/llvm-project/commit/b1bc1dbea6d0423813bb73d625c6eedc040007ed
DIFF:
https://github.com/llvm/llvm-project/commit/b1bc1dbea6d0423813bb73d625c6eedc040007ed.diff
LO
https://github.com/PiotrZSL closed
https://github.com/llvm/llvm-project/pull/88735
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -400,24 +389,27 @@ And the compilation process for module units are like:
mod1.cppm -> clang++ mod1.cppm ... -> mod1.pcm --,--> clang++
mod1.pcm ... -> mod1.o -+
src2.cpp +> clang++
src2.cpp ---> sr
@@ -633,36 +631,36 @@ example:
// module M's interface, so is discarded
int c = use_h(); // OK
-In the above example, the function definition of ``N::g`` is elided from the
Reduced
-BMI of ``M.cppm``. Then the use of ``use_g`` in
jhuber6 wrote:
>
> Maybe. The message is emitted on the host, so there is something wrong with
> the host code or runtime library.
This might be some issue with the host codegen actually.
```console
> clang malloc.c -fopenmp -fopenmp-targets=x86_64-pc-linux-gnu
>
https://github.com/arsenm updated
https://github.com/llvm/llvm-project/pull/90925
>From 4760ebce0ff7725f4bb75f5107f551d867e4db6d Mon Sep 17 00:00:00 2001
From: Ellis Hoag
Date: Thu, 2 May 2024 17:47:38 -0700
Subject: [PATCH 1/4] [modules] Accept equivalent module caches from different
symlink
https://github.com/ellishg updated
https://github.com/llvm/llvm-project/pull/90925
>From 4760ebce0ff7725f4bb75f5107f551d867e4db6d Mon Sep 17 00:00:00 2001
From: Ellis Hoag
Date: Thu, 2 May 2024 17:47:38 -0700
Subject: [PATCH 1/4] [modules] Accept equivalent module caches from different
symlink
https://github.com/ellishg edited
https://github.com/llvm/llvm-project/pull/90925
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Sean Perry
Date: 2024-05-07T15:23:50-04:00
New Revision: c9ab1d890586bd8a6a194e6a37968538b80f81bd
URL:
https://github.com/llvm/llvm-project/commit/c9ab1d890586bd8a6a194e6a37968538b80f81bd
DIFF:
https://github.com/llvm/llvm-project/commit/c9ab1d890586bd8a6a194e6a37968538b80f81bd.diff
LO
https://github.com/zibi2 closed https://github.com/llvm/llvm-project/pull/90990
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -1391,17 +1381,17 @@ with the following one:
$ clang++ -std=c++20 -xc++-system-header --precompile iostream -o
iostream.pcm
$ clang++ -std=c++20 -fmodule-file=iostream.pcm --precompile M.cppm -o M.cpp
-In the latter example, the Clang could find the BMI for the
-s
https://github.com/huangjd converted_to_draft
https://github.com/llvm/llvm-project/pull/81545
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/huangjd ready_for_review
https://github.com/llvm/llvm-project/pull/81545
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -1950,8 +1950,22 @@ ConstantLValueEmitter::tryEmitBase(const
APValue::LValueBase &base) {
if (D->hasAttr())
return CGM.GetWeakRefReference(D).getPointer();
-if (auto FD = dyn_cast(D))
- return CGM.GetAddrOfFunction(FD);
+if (auto FD = dyn_cast(D)) {
https://github.com/efriedma-quic commented:
Is it possible you could put this code into CompleteExternalDeclaration(),
instead of writing it out in every place that can refer to the address of a
function?
https://github.com/llvm/llvm-project/pull/91310
_
https://github.com/efriedma-quic edited
https://github.com/llvm/llvm-project/pull/91310
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
eaeltsin wrote:
Thanks, guarding the second specialization with the feature test macro works.
I will try to reduce the test case tomorrow, if you still need this.
https://github.com/llvm/llvm-project/pull/89807
___
cfe-commits mailing list
cfe-commit
https://github.com/fanbo-meng created
https://github.com/llvm/llvm-project/pull/91384
The XPLINK calling convention is specified in the Language Environment Vendor
Interface, chapter 22,
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.cee/cee.htm)
and in Redbook XPLi
llvmbot wrote:
@llvm/pr-subscribers-clang
@llvm/pr-subscribers-backend-systemz
Author: Fanbo Meng (fanbo-meng)
Changes
The XPLINK calling convention is specified in the Language Environment Vendor
Interface, chapter 22,
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos
tom-anders wrote:
ping - [Support for textDocument/rangesFormatting is about to be merged into
neovim](https://github.com/neovim/neovim/pull/27323), so we'll soon have at
least two editors (nvim, vscode) with support for this
https://github.com/llvm/llvm-project/pull/80180
@@ -8,109 +8,91 @@ Standard C++ Modules
Introduction
-The term ``modules`` has a lot of meanings. For the users of Clang, modules may
-refer to ``Objective-C Modules``, ``Clang C++ Modules`` (or ``Clang Header
Modules``,
-etc.) or ``Standard C++ Modules``. The im
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 27becf0c3c1e7ac4a2f2e848b44d872f1aa1db9a
7b40fa0aab937dfc0ab8db48ed93db1a5debef0b --
mejedi wrote:
cc @anakryiko
https://github.com/llvm/llvm-project/pull/91310
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Kazu Hirata
Date: 2024-05-07T12:40:19-07:00
New Revision: 65e2fab401a2da55c51d3caceae8478c33f3c60f
URL:
https://github.com/llvm/llvm-project/commit/65e2fab401a2da55c51d3caceae8478c33f3c60f
DIFF:
https://github.com/llvm/llvm-project/commit/65e2fab401a2da55c51d3caceae8478c33f3c60f.diff
L
https://github.com/fanbo-meng updated
https://github.com/llvm/llvm-project/pull/91384
>From 7b40fa0aab937dfc0ab8db48ed93db1a5debef0b Mon Sep 17 00:00:00 2001
From: Fanbo Meng
Date: Tue, 7 May 2024 13:36:38 -0400
Subject: [PATCH 1/2] [SystemZ][z/OS] Implement z/OS XPLINK ABI
The XPLINK calling
@@ -400,24 +389,27 @@ And the compilation process for module units are like:
mod1.cppm -> clang++ mod1.cppm ... -> mod1.pcm --,--> clang++
mod1.pcm ... -> mod1.o -+
src2.cpp +> clang++
src2.cpp ---> sr
jhuber6 wrote:
I'm getting the same kind of output on `main`, but the warning is mysteriously
absent.
https://github.com/llvm/llvm-project/pull/91264
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listin
https://github.com/kiranchandramohan updated
https://github.com/llvm/llvm-project/pull/90420
>From 78e91d2d84638ded51267c5e0720cc1d1d4d773b Mon Sep 17 00:00:00 2001
From: Kiran Chandramohan
Date: Fri, 26 Apr 2024 09:26:11 +
Subject: [PATCH 1/2] [Flang][Driver] Add support for -w option 1/n
@@ -738,22 +736,21 @@ the following style significantly:
import M;
... // use declarations from module M.
-The key part of the tip is to reduce the duplications from the text includes.
+Reducing the duplication from textual includes is what improves compile-time
+performan
kiranchandramohan wrote:
Done.
https://github.com/llvm/llvm-project/pull/90420
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
mizvekov wrote:
> Thanks, guarding the second specialization with the feature test macro works.
>
>
>
> I will try to reduce the test case tomorrow, if you still need this.
>
>
Thanks. If it's not too much work for you, that would be great. Otherwise, I
think a pretty good guess can be mad
@@ -925,45 +923,41 @@ In that case, you need to convert your source files (.cpp
files) to module imple
// Following off should be unchanged.
...
-The module implementation unit will import the primary module implicitly.
-We don't include any headers in the module implemen
https://github.com/katzdm edited https://github.com/llvm/llvm-project/pull/89565
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
hdoc wrote:
>From my reading of the Doxygen documentation it seems like anything goes
>except putting the doc comment inside the actual body of a function. That
>being said, I think that change is out of the scope of this PR because it
>would likely require modifications to the Clang comment-t
dwblaikie wrote:
Presumably this'll be split out into separate reviews for the components here?
(I'd guess llvm-mc then clang integrated assembler, with readobj and yaml2obj
in any order/don't have dependencies, unless they're needed for testing, in
which case I guess they come first?)
I hesi
dwblaikie wrote:
Oh, and I take it there's no /official/ extension space in the SHT_* space? The
intent is to standardize it where it lies? (like use 20 for the shipped
version? Or eventually get some lower designation?) I understand tnhe hesitance
to use "SHT_LLVM" or the like (though equally
rnk wrote:
I played with the idea of using LLVM packed structs (`<{ i129 }>`) to represent
something like this, but they don't work the way I expected them to do:
https://godbolt.org/z/M6hMYYhax
LLVM DataLayout's idea of `sizeof(i129)` is still rounded up from 17 bytes to
32 bytes.
Using byt
https://github.com/yxsamliu approved this pull request.
https://github.com/llvm/llvm-project/pull/85672
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
adrian-prantl wrote:
This broke several tests in the LLDB testsuite, I'm going to have to revert
this.
https://green.lab.llvm.org/job/llvm.org/view/LLDB/job/as-lldb-cmake/3480/
https://github.com/llvm/llvm-project/pull/81642
___
cfe-commits mailing li
aheejin wrote:
According to https://webassembly.org/features/, EH is supported from node v17,
which is also Emscripten test infra requires:
https://github.com/emscripten-core/emscripten/blob/2fefc1911e2e6265174c3fd5da38c8e9ab7abb60/test/common.py#L866-L868
So EH tests should have been already
Author: Heejin Ahn
Date: 2024-05-07T13:02:31-07:00
New Revision: dca3a6e562e012940c2b62a4d8dae3afec09caa4
URL:
https://github.com/llvm/llvm-project/commit/dca3a6e562e012940c2b62a4d8dae3afec09caa4
DIFF:
https://github.com/llvm/llvm-project/commit/dca3a6e562e012940c2b62a4d8dae3afec09caa4.diff
LO
https://github.com/aheejin closed
https://github.com/llvm/llvm-project/pull/91299
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -8,109 +8,91 @@ Standard C++ Modules
Introduction
-The term ``modules`` has a lot of meanings. For the users of Clang, modules may
-refer to ``Objective-C Modules``, ``Clang C++ Modules`` (or ``Clang Header
Modules``,
-etc.) or ``Standard C++ Modules``. The im
Author: Adrian Prantl
Date: 2024-05-07T13:03:14-07:00
New Revision: 2e4abfae57f81e2bb23fc654d6edbaeae51ae10a
URL:
https://github.com/llvm/llvm-project/commit/2e4abfae57f81e2bb23fc654d6edbaeae51ae10a
DIFF:
https://github.com/llvm/llvm-project/commit/2e4abfae57f81e2bb23fc654d6edbaeae51ae10a.diff
llvmbot wrote:
@llvm/pr-subscribers-clang-tools-extra
Author: Krystian Stasiowski (sdkrystian)
Changes
Reapplies #81642
---
Patch is 164.19 KiB, truncated to 20.00 KiB below, full version:
https://github.com/llvm/llvm-project/pull/91393.diff
26 Files Affected:
- (modified) clang-tool
AaronBallman wrote:
I think I've addressed all of the feedback (thank you all for the
improvements!), except for the suggestion from @Endilll to switch to using
italics rather than code font. I think the suggestion is a good one, but it's a
time-consuming edit that doesn't change the meaning o
diggerlin wrote:
> @diggerlin ,
>
> > > can we implement -fcomplex-ppc-gnu-abi as "-msoft-float" ? what is your
> > > opinion ?
> > > that was not the intent here and we need to consultant ABI reference
> > > regrading the same ,before we decide on implementation .
I think I do not express c
https://github.com/diggerlin approved this pull request.
https://github.com/llvm/llvm-project/pull/77732
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
MaskRay wrote:
> Thanks for the additional context. My main concern is that we're undoing the
> consensus of [reviews.llvm.org/D45164](https://reviews.llvm.org/D45164) which
> if I've understood the comments properly was "There is a reasonable
> expectation that compiled (not assembled) code s
@@ -2893,7 +2915,6 @@ static void RenderFloatingPointOptions(const ToolChain
&TC, const Driver &D,
AssociativeMath = false;
ReciprocalMath = false;
SignedZeros = true;
- FPContract = "on";
zahiraam wrote:
Not quite sure why this is remo
adrian-prantl wrote:
How did you address the LLDB test failures?
https://github.com/llvm/llvm-project/pull/91393
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/efriedma-quic edited
https://github.com/llvm/llvm-project/pull/91384
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -529,9 +529,325 @@ bool SystemZTargetCodeGenInfo::isVectorTypeBased(const
Type *Ty,
return false;
}
+//===--===//
+// z/OS XPLINK ABI Implementation
+//===
https://github.com/efriedma-quic commented:
At first glance, making a separate ABI seemed weird, but I guess it's pretty
different from the normal SystemZ ABI.
https://github.com/llvm/llvm-project/pull/91384
___
cfe-commits mailing list
cfe-commits@li
@@ -529,9 +529,325 @@ bool SystemZTargetCodeGenInfo::isVectorTypeBased(const
Type *Ty,
return false;
}
+//===--===//
+// z/OS XPLINK ABI Implementation
+//===
@@ -529,9 +529,325 @@ bool SystemZTargetCodeGenInfo::isVectorTypeBased(const
Type *Ty,
return false;
}
+//===--===//
+// z/OS XPLINK ABI Implementation
+//===
sdkrystian wrote:
@adrian-prantl While I'm not 100% certain of this, I _think_ modules are cached
between test runs for LLDB (the only way I was able to reproduce the crash was
by precompiling modules with clang built from the commit before this one, and
then deserializing with clang built fro
Author: Ellis Hoag
Date: 2024-05-07T13:55:44-07:00
New Revision: 2ad6917c4c524576405f2146424911fd9adb3528
URL:
https://github.com/llvm/llvm-project/commit/2ad6917c4c524576405f2146424911fd9adb3528
DIFF:
https://github.com/llvm/llvm-project/commit/2ad6917c4c524576405f2146424911fd9adb3528.diff
LO
https://github.com/ellishg closed
https://github.com/llvm/llvm-project/pull/90925
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/asl edited https://github.com/llvm/llvm-project/pull/91258
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/asl approved this pull request.
Thanks!
https://github.com/llvm/llvm-project/pull/91258
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/asl closed https://github.com/llvm/llvm-project/pull/91258
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Marian Buschsieweke
Date: 2024-05-07T13:58:13-07:00
New Revision: bc8a42762057d7036f6871211e62b1c3efb2738a
URL:
https://github.com/llvm/llvm-project/commit/bc8a42762057d7036f6871211e62b1c3efb2738a
DIFF:
https://github.com/llvm/llvm-project/commit/bc8a42762057d7036f6871211e62b1c3efb2738a
benisxdxd wrote:
@smithp35 The system i'm interacting with has a GCC plugin that uses r4 and r5
for custom software mitigations against exploitation.
I need a way to inform LLVM to keep this registers untouched so I don't
interfere and cause a corruption.
By reserving those registers I will be
github-actions[bot] wrote:
@maribu 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 build,
efriedma-quic wrote:
> I didn't want the current set of changes to go stale.
How many changes are we talking about here? If it's just the tan() ones,
that's fine; it probably makes sense to land constrained-tan separately anyway.
https://github.com/llvm/llvm-project/pull/90276
___
farzonl wrote:
> > I didn't want the current set of changes to go stale.
>
> How many changes are we talking about here? If it's just the tan() ones,
> that's fine; it probably makes sense to land constrained-tan separately
> anyway.
There are 4 for tan. There will be more for the other intri
https://github.com/justincady created
https://github.com/llvm/llvm-project/pull/91400
This is a renewed attempt to land @toddlipcon's D34654. The comments on
that patch indicate a broad desire for some ability to ignore headers.
After considering various options, including migrating to std::reg
llvmbot wrote:
@llvm/pr-subscribers-clang-tidy
@llvm/pr-subscribers-clang-tools-extra
Author: Justin Cady (justincady)
Changes
This is a renewed attempt to land @toddlipcon's D34654. The comments on
that patch indicate a broad desire for some ability to ignore headers.
After considering v
https://github.com/pogo59 created
https://github.com/llvm/llvm-project/pull/91401
Debug-info metadata does not have a strictly defined order. Check that elements
are linked to each other correctly, not that metadata appears in a particular
order.
>From 8e23d2bea291ad003417f7f1af6e2143e1352bb2
llvmbot wrote:
@llvm/pr-subscribers-coroutines
Author: Paul T Robinson (pogo59)
Changes
Debug-info metadata does not have a strictly defined order. Check that elements
are linked to each other correctly, not that metadata appears in a particular
order.
---
Full diff: https://github.com/
pogo59 wrote:
This test was failing in our downstream repo because the metadata didn't come
out in exactly the same order.
https://github.com/llvm/llvm-project/pull/91401
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/c
https://github.com/rniwa created https://github.com/llvm/llvm-project/pull/91402
None
>From 141d4b791469f23e9226ff7325131af1a5c2d8bb Mon Sep 17 00:00:00 2001
From: Ryosuke Niwa
Date: Tue, 7 May 2024 14:10:57 -0700
Subject: [PATCH] Fix a typo in webkit.NoUncountedMemberChecker.
---
.../Checker
llvmbot wrote:
@llvm/pr-subscribers-clang-static-analyzer-1
@llvm/pr-subscribers-clang
Author: Ryosuke Niwa (rniwa)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/91402.diff
1 Files Affected:
- (modified)
clang/lib/StaticAnalyzer/Checkers/WebKit/NoUncountedMembersCh
https://github.com/efriedma-quic approved this pull request.
Okay. I mostly just want to make sure the plan isn't "land all the intrinsics
from the RFC, then eventually investigate the constrained intrinsics".
LGTM
https://github.com/llvm/llvm-project/pull/90276
__
https://github.com/MatzeB edited https://github.com/llvm/llvm-project/pull/91275
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/haoNoQ approved this pull request.
Nice LGTM!
You could test this patch by pasting the warning into one of the
`expected-warning{{}}` clauses in the tests but I honestly don't think it's all
that important for a patch like this.
https://github.com/llvm/llvm-project/pull/914
@@ -2893,7 +2915,6 @@ static void RenderFloatingPointOptions(const ToolChain
&TC, const Driver &D,
AssociativeMath = false;
ReciprocalMath = false;
SignedZeros = true;
- FPContract = "on";
andykaylor wrote:
It was unnecessary. Only one
https://github.com/rniwa updated https://github.com/llvm/llvm-project/pull/91402
>From c3a6cff7d1cb25da8dad0dfc7cb9b0eb694967c5 Mon Sep 17 00:00:00 2001
From: Brianna Fan
Date: Tue, 7 May 2024 14:10:57 -0700
Subject: [PATCH] Fix a typo in webkit.NoUncountedMemberChecker.
---
.../Checkers/WebKi
alexey-bataev wrote:
Hmm, hard to tell, need to debug it.
https://github.com/llvm/llvm-project/pull/91264
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
MaskRay wrote:
Thanks for the comments.
The syntax `-Wa,--crel -Wa,--experimental-crel` (or
`-Wa,--crel,--experimental-crel`) might seem cumbersome, it serves a purpose:
* `-Wa,--experimental-crel`: no effect
* `-Wa,--crel`: driver error. Make sure users acknowledge the non-standard
status.
*
https://github.com/python3kgae updated
https://github.com/llvm/llvm-project/pull/89836
>From 4d8c72688656fe3b2ce8817087d8cf7352b5876b Mon Sep 17 00:00:00 2001
From: Xiang Li
Date: Tue, 23 Apr 2024 17:49:02 -0400
Subject: [PATCH 01/10] [HLSL] Support packoffset attribute in AST
Add HLSLPackOffs
rjmccall wrote:
Hmm. I think this is actually pretty different from the `bool` pattern.
Suppose we're talking about `_BitInt(N)`. Let `BYTES := ceil(N/8)`, and let
`BITS := BYTES * 8`.
The problem being presented here is this:
1. For at least some values of `N`, we cannot use LLVM's `iN` f
@@ -1,22 +1,113 @@
+// NOTE: Assertions have been autogenerated by utils/update_cc_test_checks.py
UTC_ARGS: --version 4
// REQUIRES: amdgpu-registered-target
// RUN: %clang_cc1 %s -emit-llvm -O0 -o - \
-// RUN: -triple=amdgcn-amd-amdhsa | opt -S | FileCheck %s
+// RUN: -tr
@@ -4408,6 +4409,42 @@ Target-Specific Extensions
Clang supports some language features conditionally on some targets.
+AMDGPU Language Extensions
+--
+
+__builtin_amdgcn_fence
+^^
+
+``__builtin_amdgcn_fence`` emits a fence.
+
+* `
https://github.com/bogner approved this pull request.
https://github.com/llvm/llvm-project/pull/90276
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jhuber6 wrote:
> Hmm, hard to tell, need to debug it.
Somehow when I print it in the runtime it shows up as garbage, but the actual
region seems to get correct values. There shouldn't be anything in-between the
arguments I'm printing and the kernel launch however so I'm stumped.
https://githu
rjmccall wrote:
If you want to do things that way, you will need to (1) generalize CodeGenTypes
with a new API that will return this load/store type when applicable and (2)
look at all the places we call `ConvertTypeForMem`, `EmitToMemory`, and
`EmitFromMemory` to make sure they do the right t
https://github.com/bharadwajy created
https://github.com/llvm/llvm-project/pull/91407
This change set restores the PR #90809 that was reverted to address ASAN
failures and includes a fix for the ASAN failures.
Following is the description of the change:
An earlier commit provided a way to de
llvmbot wrote:
@llvm/pr-subscribers-clang-driver
Author: S. Bharadwaj Yadavalli (bharadwajy)
Changes
This change set restores the PR #90809 that was reverted to address
ASAN failures and includes a fix for the ASAN failures.
Following is the description of the change:
An earlier commit
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: S. Bharadwaj Yadavalli (bharadwajy)
Changes
This change set restores the PR #90809 that was reverted to address
ASAN failures and includes a fix for the ASAN failures.
Following is the description of the change:
An earlier commit provid
301 - 400 of 488 matches
Mail list logo
