https://github.com/pogo59 commented:
Thanks for the heads-up @RKSimon I've made suggestions for consistency with
existing practice in emmintrin.h which I've adopted in the latest revision to
#83316.
I'm unsure how replacing a function declaration with an \fn directive will play
with our docum
@@ -2940,6 +2940,84 @@ _mm_movemask_ps(__m128 __a)
return __builtin_ia32_movmskps((__v4sf)__a);
}
+/* Compare */
+#define _CMP_EQ_OQ0x00 /* Equal (ordered, non-signaling) */
+#define _CMP_LT_OS0x01 /* Less-than (ordered, signaling) */
+#define _CMP_LE_OS0x02 /*
@@ -4745,6 +4745,77 @@ static __inline__ __m128d __DEFAULT_FN_ATTRS
_mm_castsi128_pd(__m128i __a) {
return (__m128d)__a;
}
+/// Compares each of the corresponding double-precision values of two
+///128-bit vectors of [2 x double], using the operation specified by the
+/
@@ -2940,6 +2940,84 @@ _mm_movemask_ps(__m128 __a)
return __builtin_ia32_movmskps((__v4sf)__a);
}
+/* Compare */
+#define _CMP_EQ_OQ0x00 /* Equal (ordered, non-signaling) */
+#define _CMP_LT_OS0x01 /* Less-than (ordered, signaling) */
+#define _CMP_LE_OS0x02 /*
@@ -4745,6 +4745,77 @@ static __inline__ __m128d __DEFAULT_FN_ATTRS
_mm_castsi128_pd(__m128i __a) {
return (__m128d)__a;
}
+/// Compares each of the corresponding double-precision values of two
+///128-bit vectors of [2 x double], using the operation specified by the
+/
Author: Yaxun (Sam) Liu
Date: 2024-03-08T10:50:38-05:00
New Revision: b46f980454d5ceafc8dab37dbdb1011e333ae6de
URL:
https://github.com/llvm/llvm-project/commit/b46f980454d5ceafc8dab37dbdb1011e333ae6de
DIFF:
https://github.com/llvm/llvm-project/commit/b46f980454d5ceafc8dab37dbdb1011e333ae6de.dif
https://github.com/yxsamliu closed
https://github.com/llvm/llvm-project/pull/83870
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/yxsamliu closed
https://github.com/llvm/llvm-project/pull/83306
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
yxsamliu wrote:
since zstd has comparable compression rate and is much faster, we will use
zstd. close this PR.
https://github.com/llvm/llvm-project/pull/83306
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mail
zyn0217 wrote:
Thanks. That explains now :)
https://github.com/llvm/llvm-project/pull/84459
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
erichkeane wrote:
> Thanks. That explains now :)
No problem! Feel free to change a bunch of them, I'm sure we pass by copy
quite a bit, I chased out many of them a while back, but I'm sure i didnt get
them all.
https://github.com/llvm/llvm-project/pull/84459
_
https://github.com/yxsamliu updated
https://github.com/llvm/llvm-project/pull/83605
>From 16796bc8eb3b32436903db4b689d4cb9cfc348d8 Mon Sep 17 00:00:00 2001
From: "Yaxun (Sam) Liu"
Date: Fri, 1 Mar 2024 13:16:45 -0500
Subject: [PATCH] [HIP] add --offload-compression-level= option
Added --offloa
yxsamliu wrote:
zstd developers suggest to enable long distance matching (LDM), i.e. the
`--long` option. I updated the PR with the change, and tested that it works
well for bundle entry sizes range from 1KB to 20MB, for both compression rate
and compression/decompression speed.
https://githu
jhuber6 wrote:
Should an option like in https://github.com/llvm/llvm-project/pull/84337 be
added for the new driver?
https://github.com/llvm/llvm-project/pull/83605
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin
https://github.com/yxsamliu edited
https://github.com/llvm/llvm-project/pull/83605
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/pogo59 commented:
The example for `\fn` in the [doxygen
documentation](https://www.doxygen.nl/manual/commands.html#cmdfn) puts the
directive at the top of the comment block, not at the end. Do we know whether
putting it at the end will produce the expected result?
https://g
yxsamliu wrote:
> Should an option like in #84337 be added for the new driver?
Yes please
https://github.com/llvm/llvm-project/pull/83605
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commi
yxsamliu wrote:
> > Should an option like in #84337 be added for the new driver?
>
> Yes please
Oh. I can add it
https://github.com/llvm/llvm-project/pull/83605
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/ma
andreasfertig wrote:
> @andreasfertig Will you need us to merge that for you?
@cor3ntin: It looks like I need you, yes. I can only close the PR :-/
https://github.com/llvm/llvm-project/pull/84193
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
@@ -638,6 +643,31 @@ SDValue BPFTargetLowering::LowerDYNAMIC_STACKALLOC(SDValue
Op,
return DAG.getMergeValues(Ops, SDLoc());
}
+SDValue BPFTargetLowering::LowerADDRSPACECAST(SDValue Op,
+ SelectionDAG &DAG) const {
+ auto *ACast
shafik wrote:
Can we please get more descriptive summaries in the future. We should at a
minimum state 1) what the underlying problem is 2) what the approach for fixing
the problem is.
In this case the title describes the problem but it would be nice to have a
summary of the fix as well. So f
Author: Andreas Fertig
Date: 2024-03-08T08:10:20-08:00
New Revision: 35d3b33ba5c9b90443ac985f2521b78f84b611fe
URL:
https://github.com/llvm/llvm-project/commit/35d3b33ba5c9b90443ac985f2521b78f84b611fe
DIFF:
https://github.com/llvm/llvm-project/commit/35d3b33ba5c9b90443ac985f2521b78f84b611fe.diff
https://github.com/erichkeane closed
https://github.com/llvm/llvm-project/pull/84193
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jthackray wrote:
Linux and Windows builds are passing, but someone has left a trailing
whitespace character at clang/docs/ReleaseNotes.rst:407 (not me), so I'll merge
anyway.
https://github.com/llvm/llvm-project/pull/84485
___
cfe-commits mailing lis
github-actions[bot] wrote:
@andreasfertig 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
https://github.com/jthackray closed
https://github.com/llvm/llvm-project/pull/84485
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Jonathan Thackray
Date: 2024-03-08T16:11:36Z
New Revision: 81601391369c267216199db3f7fcb9864ccf6fec
URL:
https://github.com/llvm/llvm-project/commit/81601391369c267216199db3f7fcb9864ccf6fec
DIFF:
https://github.com/llvm/llvm-project/commit/81601391369c267216199db3f7fcb9864ccf6fec.diff
https://github.com/kpneal closed https://github.com/llvm/llvm-project/pull/74883
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
kpneal wrote:
OK, I'll head in the direction you've pointed. Thanks for your time!
https://github.com/llvm/llvm-project/pull/74883
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/jthackray edited
https://github.com/llvm/llvm-project/pull/84485
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Fznamznon wrote:
> Can we please get more descriptive summaries in the future.
Sure, sorry about that.
https://github.com/llvm/llvm-project/pull/84343
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listi
https://github.com/SchrodingerZhu created
https://github.com/llvm/llvm-project/pull/84509
None
>From 76e99fd03b1fb51b59f0f4dbd5eefaff5e46175f Mon Sep 17 00:00:00 2001
From: Schrodinger ZHU Yifan
Date: Fri, 8 Mar 2024 11:14:39 -0500
Subject: [PATCH] [libc][libunwind] support build libunwind wit
https://github.com/SchrodingerZhu edited
https://github.com/llvm/llvm-project/pull/84509
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
pogo59 wrote:
> I think so - we're just losing the extra info about -1/0 or 1/0 result values?
That's my understanding. I haven't actually tried regenerating the tooltips to
check.
https://github.com/llvm/llvm-project/pull/83316
___
cfe-commits maili
Author: erichkeane
Date: 2024-03-08T08:19:15-08:00
New Revision: c54e0524eeffcf2c5428cd2bc0449a1989e82cd8
URL:
https://github.com/llvm/llvm-project/commit/c54e0524eeffcf2c5428cd2bc0449a1989e82cd8
DIFF:
https://github.com/llvm/llvm-project/commit/c54e0524eeffcf2c5428cd2bc0449a1989e82cd8.diff
LO
@@ -1405,11 +1413,12 @@ static __inline__ __m128d __DEFAULT_FN_ATTRS
_mm_cvtss_sd(__m128d __a,
/// Converts the two double-precision floating-point elements of a
///128-bit vector of [2 x double] into two signed 32-bit integer values,
-///returned in the lower 64 bits
https://github.com/guillem-bartina-sonarsource created
https://github.com/llvm/llvm-project/pull/84515
The current diagnostic message is `unused member function A` for every kind of
method, including constructors. The idea is to refine the message to `unused
constructor A` when the method is a
github-actions[bot] wrote:
Thank you for submitting a Pull Request (PR) to the LLVM Project!
This PR will be automatically labeled and the relevant teams will be
notified.
If you wish to, you can add reviewers by using the "Reviewers" section on this
page.
If this is not working for you, it
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: None (guillem-bartina-sonarsource)
Changes
The current diagnostic message is `unused member function A` for every kind of
method, including constructors. The idea is to refine the message to `unused
constructor A` when the method is a con
=?utf-8?q?Donát?= Nagy ,
=?utf-8?q?Donát?= Nagy
Message-ID:
In-Reply-To:
steakhal wrote:
> I feel that I'm getting bogged down in this area with changes that are more
> general than what's strictly necessary and only tangentially related to my
> real goals...
>
> I'm not familiar with the u
https://github.com/nickdesaulniers commented:
Rather than have a `-f` flag to opt into this extension, I think instead you
should just make it always available, then have tests that it can be used, but
will trigger diagnostics under `-Wpedantic` since it's technically a language
extension (IIU
https://github.com/nickdesaulniers edited
https://github.com/llvm/llvm-project/pull/84428
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,43 @@
+// RUN: %clang_cc1 %s -verify=c -fsyntax-only -fflex-array-extensions
+
+// The test checks that flexible array members do not emit warnings when
+// -fflex-array-extensions when used in a union or alone in a structure.
+
+struct already_hidden {
+ int a;
-
@@ -1405,11 +1413,12 @@ static __inline__ __m128d __DEFAULT_FN_ATTRS
_mm_cvtss_sd(__m128d __a,
/// Converts the two double-precision floating-point elements of a
///128-bit vector of [2 x double] into two signed 32-bit integer values,
-///returned in the lower 64 bits
https://github.com/yxsamliu updated
https://github.com/llvm/llvm-project/pull/83605
>From 60faf7f657fdcc00edfa0a1813d1e2746c341ef1 Mon Sep 17 00:00:00 2001
From: "Yaxun (Sam) Liu"
Date: Fri, 1 Mar 2024 13:16:45 -0500
Subject: [PATCH] [HIP] add --offload-compression-level= option
Added --offloa
yxsamliu wrote:
> Should an option like in #84337 be added for the new driver?
added the option to linker wrapper
https://github.com/llvm/llvm-project/pull/83605
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/ma
https://github.com/jhuber6 commented:
Looks fine to me, I'll wait a bit to see if Artem or Fangrui have anything to
add.
https://github.com/llvm/llvm-project/pull/83605
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi
https://github.com/balazske approved this pull request.
I am not totally sure but this looks correct with the new variable names and
there are some tests for the new case.
https://github.com/llvm/llvm-project/pull/84201
___
cfe-commits mailing list
cf
https://github.com/balazske edited
https://github.com/llvm/llvm-project/pull/84201
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -83,6 +83,8 @@ class StateUpdateReporter {
AssumedUpperBound = UpperBoundVal;
}
+ bool assumedNonNegative() { return AssumedNonNegative; }
balazske wrote:
This should be called `getAssumedNonNegative` or `hasAssumedNonNegative` (but
the naming rule
https://github.com/andreasfertig created
https://github.com/llvm/llvm-project/pull/84519
This is a follow-up of #84064. It turned out that a coroutine-lambda with a
`promise_type` and a user-defined constructor ignores the `this` pointer. Per
http://eel.is/c++draft/dcl.fct.def.coroutine#4, in
llvmbot wrote:
@llvm/pr-subscribers-coroutines
Author: Andreas Fertig (andreasfertig)
Changes
This is a follow-up of #84064. It turned out that a coroutine-lambda
with a `promise_type` and a user-defined constructor ignores the `this`
pointer. Per http://eel.is/c++draft/dcl.fct.def.corou
andreasfertig wrote:
@ChuanqiXu9 here is a dedicated patch to support a `promise_type` with a
user-provided constructor in a coroutine used with a lambda.
https://github.com/llvm/llvm-project/pull/84519
___
cfe-commits mailing list
cfe-commits@lists.l
https://github.com/yxsamliu updated
https://github.com/llvm/llvm-project/pull/83605
>From 78ad578a19d2a3585f20ab64d364a46a584ec035 Mon Sep 17 00:00:00 2001
From: "Yaxun (Sam) Liu"
Date: Fri, 1 Mar 2024 13:16:45 -0500
Subject: [PATCH] [HIP] add --offload-compression-level= option
Added --offloa
https://github.com/Sirraide created
https://github.com/llvm/llvm-project/pull/84520
This updates a few warnings that were diagnosing no arguments for a `...`
variadic macro parameter as a GNU extension when it actually is a C++20/C23
extension now.
This fixes #84495.
>From 502692869e3105bb2c
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: None (Sirraide)
Changes
This updates a few warnings that were diagnosing no arguments for a `...`
variadic macro parameter as a GNU extension when it actually is a C++20/C23
extension now.
This fixes #84495.
---
Full diff: https://githu
https://github.com/Sirraide updated
https://github.com/llvm/llvm-project/pull/84520
>From 502692869e3105bb2c55955bc4baff63b1475770 Mon Sep 17 00:00:00 2001
From: Sirraide
Date: Fri, 8 Mar 2024 18:15:07 +0100
Subject: [PATCH 1/2] [Clang] Update missing varargs arg extension warnings
---
clang/
Author: Piotr Zegar
Date: 2024-03-08T18:34:26+01:00
New Revision: 9fb552812c65a13cd19eedea1cc2ef739ad652e9
URL:
https://github.com/llvm/llvm-project/commit/9fb552812c65a13cd19eedea1cc2ef739ad652e9
DIFF:
https://github.com/llvm/llvm-project/commit/9fb552812c65a13cd19eedea1cc2ef739ad652e9.diff
L
https://github.com/PiotrZSL closed
https://github.com/llvm/llvm-project/pull/84236
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/ymand updated https://github.com/llvm/llvm-project/pull/84499
>From 3b20e1823753ab46e3e259d3d8c727dea91ce1d4 Mon Sep 17 00:00:00 2001
From: Yitzhak Mandelbaum
Date: Fri, 8 Mar 2024 15:19:14 +
Subject: [PATCH] [clang][dataflow] Refactor processing of terminator element
Thi
topperc wrote:
@jrtc27 does this look better now?
https://github.com/llvm/llvm-project/pull/83896
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/dobbelaj-snps approved this pull request.
lgtm
https://github.com/llvm/llvm-project/pull/84386
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/kees closed https://github.com/llvm/llvm-project/pull/80089
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
kees wrote:
With PR #82432 landed, this PR is redundant. Thanks for changing the option
name! Closing...
https://github.com/llvm/llvm-project/pull/80089
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/lis
@@ -0,0 +1,43 @@
+// RUN: %clang_cc1 %s -verify=c -fsyntax-only -fflex-array-extensions
+
+// The test checks that flexible array members do not emit warnings when
+// -fflex-array-extensions when used in a union or alone in a structure.
+
+struct already_hidden {
+ int a;
-
nikic wrote:
Shouldn't plain `-fsanitize=undefined` disable this sanitizer by default
(requiring explicit opt-in)? In `-fwrapv` mode this is not undefined behavior,
so `-fsanitize=undefined` should not complain about it.
https://github.com/llvm/llvm-project/pull/82432
kees wrote:
> Rather than have a `-f` flag to opt into this extension, I think instead you
> should just make it always available, then have tests that it can be used,
> but will trigger diagnostics under `-Wpedantic` since it's technically a
> language extension (IIUC).
I didn't do this beca
bgra8 wrote:
Thanks a lot @sdkrystian ! We have a reducer session running! We'll post here
when we have it!
https://github.com/llvm/llvm-project/pull/83842
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/
https://github.com/benlangmuir created
https://github.com/llvm/llvm-project/pull/84525
Stop overriding -working-directory to CWD during argument parsing, which should
no longer necessary after we set the VFS working directory, and set FSOpts
correctly after parsing arguments so that working-di
https://github.com/farzonl created
https://github.com/llvm/llvm-project/pull/84526
This change implements lowering for #70076, #70100, #70072, & #70102
`CGBuiltin.cpp` - - simplify `lerp` intrinsic
`IntrinsicsDirectX.td` - simplify `lerp` intrinsic
`SemaChecking.cpp` - remove unnecessary check
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Ben Langmuir (benlangmuir)
Changes
Stop overriding -working-directory to CWD during argument parsing, which should
no longer necessary after we set the VFS working directory, and set FSOpts
correctly after parsing arguments so that workin
llvmbot wrote:
@llvm/pr-subscribers-llvm-ir
@llvm/pr-subscribers-hlsl
Author: Farzon Lotfi (farzonl)
Changes
This change implements lowering for #70076, #70100, #70072, & #70102
`CGBuiltin.cpp` - - simplify `lerp` intrinsic
`IntrinsicsDirectX.td` - simplify `lerp` intrinsic
`SemaChecking.
llvmbot wrote:
@llvm/pr-subscribers-backend-directx
Author: Farzon Lotfi (farzonl)
Changes
This change implements lowering for #70076, #70100, #70072, & #70102
`CGBuiltin.cpp` - - simplify `lerp` intrinsic
`IntrinsicsDirectX.td` - simplify `lerp` intrinsic
`SemaChecking.cpp` - remove unne
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Farzon Lotfi (farzonl)
Changes
This change implements lowering for #70076, #70100, #70072, & #70102
`CGBuiltin.cpp` - - simplify `lerp` intrinsic
`IntrinsicsDirectX.td` - simplify `lerp` intrinsic
`SemaChecking.cpp` - remove unnecessary ch
@@ -0,0 +1,43 @@
+// RUN: %clang_cc1 %s -verify=c -fsyntax-only -fflex-array-extensions
+
+// The test checks that flexible array members do not emit warnings when
+// -fflex-array-extensions when used in a union or alone in a structure.
+
+struct already_hidden {
+ int a;
-
https://github.com/nickdesaulniers edited
https://github.com/llvm/llvm-project/pull/84428
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
cor3ntin wrote:
LGTM, thanks!
https://github.com/llvm/llvm-project/pull/81014
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/cor3ntin approved this pull request.
https://github.com/llvm/llvm-project/pull/81014
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: erichkeane
Date: 2024-03-08T10:16:34-08:00
New Revision: 5a95378659506b0ce94ceb79a43477e73c9756f4
URL:
https://github.com/llvm/llvm-project/commit/5a95378659506b0ce94ceb79a43477e73c9756f4
DIFF:
https://github.com/llvm/llvm-project/commit/5a95378659506b0ce94ceb79a43477e73c9756f4.diff
LO
Sirraide wrote:
@erichkeane @AaronBallman Do we want to figure out what to do wrt OpenMP’s
`assume` attribute before we merge this, or do we want to decide on that after
this is merged? Currently, only `[[assume]]` is treated as the standard
attribute, and `[[clang::assume]]` or `__attribute__
@@ -226,6 +226,47 @@ HLSLToolChain::TranslateArgs(const DerivedArgList &Args,
StringRef BoundArch,
A->claim();
continue;
}
+if (A->getOption().getID() == options::OPT_dxc_hlsl_version) {
+ // Translate -HV into -std for llvm
+ // depending on the
https://github.com/Artem-B edited
https://github.com/llvm/llvm-project/pull/83605
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/Artem-B approved this pull request.
LGTM.
https://github.com/llvm/llvm-project/pull/83605
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -2863,3 +2863,18 @@ void tools::addOutlineAtomicsArgs(const Driver &D, const
ToolChain &TC,
CmdArgs.push_back("+outline-atomics");
}
}
+
+void tools::addOffloadCompressArgs(const llvm::opt::ArgList &TCArgs,
+ llvm::opt::ArgStringList
https://github.com/jroelofs approved this pull request.
https://github.com/llvm/llvm-project/pull/84405
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/jroelofs edited
https://github.com/llvm/llvm-project/pull/84405
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -85,7 +85,21 @@ int hoo(void) {
}
+// This should generate one target version but no resolver.
+__attribute__((target_version("default"))) int
unused_with_forward_default_decl(void);
+__attribute__((target_version("mops"))) int
unused_with_forward_default_decl(void) { re
nickdesaulniers wrote:
> I didn't do this because it seemed like this would change a lot of existing
> test cases
Can you give some examples of tests that would fail? If we have tests checking
that these fail, then perhaps those tests should add `-Werror=pedantic` so that
they can continue to
https://github.com/rapidsna updated
https://github.com/llvm/llvm-project/pull/78000
>From 3d2716ad6088f600c14d6ff724aa90453130a1f7 Mon Sep 17 00:00:00 2001
From: Yeoul Na
Date: Mon, 18 Dec 2023 10:58:16 +0900
Subject: [PATCH 01/10] [BoundsSafety] Introduce CountAttributedType
CountAttributedTy
alexey-bataev wrote:
> `[[clang::assume]]` or `__attribute__((assume))` are the OpenMP one
OpenMP requires only [[omp::assume]], neither [[clang::assume]] nor
__attribute__((assume)) are OpenMP requirement.
https://github.com/llvm/llvm-project/pull/81014
___
Sirraide wrote:
> > `[[clang::assume]]` or `__attribute__((assume))` are the OpenMP one
>
> OpenMP requires only [[omp::assume]], neither [[clang::assume]] nor
> **attribute**((assume)) are OpenMP requirement.
Yeah, the weird thing is I’m not sure we support `[[omp::assume]]` at the
moment. W
alexey-bataev wrote:
> > > `[[clang::assume]]` or `__attribute__((assume))` are the OpenMP one
> >
> >
> > OpenMP requires only [[omp::assume]], neither [[clang::assume]] nor
> > **attribute**((assume)) are OpenMP requirement.
>
> Yeah, the weird thing is I’m not sure we support `[[omp::assum
Sirraide wrote:
> > > > `[[clang::assume]]` or `__attribute__((assume))` are the OpenMP one
> > >
> > >
> > > OpenMP requires only [[omp::assume]], neither [[clang::assume]] nor
> > > **attribute**((assume)) are OpenMP requirement.
> >
> >
> > Yeah, the weird thing is I’m not sure we support
alexey-bataev wrote:
> > > > > `[[clang::assume]]` or `__attribute__((assume))` are the OpenMP one
> > > >
> > > >
> > > > OpenMP requires only [[omp::assume]], neither [[clang::assume]] nor
> > > > **attribute**((assume)) are OpenMP requirement.
> > >
> > >
> > > Yeah, the weird thing is I’
Xazax-hun wrote:
Once the other reviewers are happy, this looks good to me!
https://github.com/llvm/llvm-project/pull/84469
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Sirraide wrote:
If we can come to a consensus as to what to do w/ `clang::assume` and
`__attribute__((assume))` reasonably soon, then I’ll handle `[[omp::assume]]`
in this pr as well; otherwise, I’ll open a pr for `[[omp::assume]]` tomorrow or
so.
https://github.com/llvm/llvm-project/pull/810
https://github.com/jhuber6 created
https://github.com/llvm/llvm-project/pull/84534
Summary:
The current behavior of HIP is that when --offload-device-only is set it
still bundles the outputs into a fat binary. Even though this is
different from how all the other targets handle this, it seems to
https://github.com/Xazax-hun approved this pull request.
https://github.com/llvm/llvm-project/pull/84499
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvmbot wrote:
@llvm/pr-subscribers-clang-driver
Author: Joseph Huber (jhuber6)
Changes
Summary:
The current behavior of HIP is that when --offload-device-only is set it
still bundles the outputs into a fat binary. Even though this is
different from how all the other targets handle this, i
erichkeane wrote:
> If we can come to a consensus as to what to do w/ `clang::assume` and
> `__attribute__((assume))` reasonably soon, then I’ll handle `[[omp::assume]]`
> in this pr as well; otherwise, I’ll open a pr for `[[omp::assume]]` tomorrow
> or so.
This patch is big enough as it is,
201 - 300 of 487 matches
Mail list logo
