Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
The stdexec library currently wrongly ends up using __decay as the scope of
a typename, which leads to a crash. Let's give an error instead.
PR c++/116052
gcc/cp/ChangeLog:
* mangle.cc (write_prefix): Handle TRAIT_EXPR.
On Fri, Jul 26, 2024 at 08:43:44PM +0200, Jakub Jelinek wrote:
> Yeah, I saw ARGUMENT_PACK_SELECT being used, but didn't notice that
> important
> if (arg_pack && TREE_CODE (arg_pack) == ARGUMENT_PACK_SELECT)
> arg_pack = ARGUMENT_PACK_SELECT_FROM_PACK (arg_pack);
> part of tsubst_pac
On Fri, Jul 26, 2024 at 09:49:27PM +0200, Jakub Jelinek wrote:
> On Fri, Jul 26, 2024 at 08:43:44PM +0200, Jakub Jelinek wrote:
> > Yeah, I saw ARGUMENT_PACK_SELECT being used, but didn't notice that
> > important
> > if (arg_pack && TREE_CODE (arg_pack) == ARGUMENT_PACK_SELECT)
> > a
On 7/26/24 12:43 PM, Raphael Zinsly wrote:
On Fri, Jul 26, 2024 at 2:00 PM Jeff Law wrote:
On 7/24/24 12:00 PM, Raphael Moreira Zinsly wrote:
...
diff --git a/gcc/config/riscv/riscv.md b/gcc/config/riscv/riscv.md
index 46c46039c33..5780c5abacf 100644
--- a/gcc/config/riscv/riscv.md
+++ b/gc
On 7/24/24 12:00 PM, Raphael Moreira Zinsly wrote:
Move riscv_v_adjust_scalable_frame () in preparation for the stack clash
protection support.
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_v_adjust_scalable_frame): Move
closer to riscv_expand_prologue.
Guessing the point is
On Fri, 26 Jul 2024, Jakub Jelinek wrote:
> On Fri, Jul 26, 2024 at 09:49:27PM +0200, Jakub Jelinek wrote:
> > On Fri, Jul 26, 2024 at 08:43:44PM +0200, Jakub Jelinek wrote:
> > > Yeah, I saw ARGUMENT_PACK_SELECT being used, but didn't notice that
> > > important
> > > if (arg_pack && TREE_C
Hi,
when the source mode is potentially larger than one vector (e.g. an
LMUL2 mode for VLEN=128) we don't know which vector the subreg actually
refers to. For zvl128b and LMUL=2 the subreg in (subreg:V2DI (reg:V4DI))
could actually be the a full (high) vector register of a two-register
group (at
On Fri, Jul 26, 2024 at 04:42:36PM -0400, Patrick Palka wrote:
> > // P2963R3 - Ordering of constraints involving fold expressions
> > // { dg-do compile { target c++20 } }
> >
> > template concept C = (__is_same (T, int) && ...);
> > template
> > struct S {
> > template requires (C)
> > st
On 7/24/24 12:00 PM, Raphael Moreira Zinsly wrote:
This implements stack-clash protection for riscv, with
riscv_allocate_and_probe_stack_space being based of
aarch64_allocate_and_probe_stack_space from aarch64's implementation.
We enforce the probing interval and the guard size to always be eq
On 7/24/24 12:00 PM, Raphael Moreira Zinsly wrote:
Adds basic support to vector stack-clash protection using a loop to do
the probing and stack adjustments.
gcc/ChangeLog:
* config/riscv/riscv.cc
(riscv_allocate_and_probe_stack_loop): New function.
(riscv_v_adjust_scal
On 7/24/24 12:00 PM, Raphael Moreira Zinsly wrote:
Add the TARGET_STACK_CLASH_PROTECTION_ALLOCA_PROBE_RANGE to riscv in
order to enable stack clash protection when using alloca.
The code and tests are the same used by aarch64.
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_compute_fram
On 7/23/24 6:39 PM, Patrick O'Neill wrote:
(define_expand "atomic_compare_and_swap"
[(match_operand:SI 0 "register_operand" "") ;; bool output
(match_operand:GPR 1 "register_operand" "") ;; val output
(match_operand:GPR 2 "memory_operand" "");; memory
- (match_operand:
On Fri, 26 Jul 2024, Jakub Jelinek wrote:
> On Fri, Jul 26, 2024 at 04:42:36PM -0400, Patrick Palka wrote:
> > > // P2963R3 - Ordering of constraints involving fold expressions
> > > // { dg-do compile { target c++20 } }
> > >
> > > template concept C = (__is_same (T, int) && ...);
> > > templat
On 7/23/24 6:15 PM, Patrick O'Neill wrote:
From: Gianluca Guida
This patch adds support for amocas.{b|h|w|d}. Support for amocas.q
(64/128 bit cas for rv32/64) will be added in a future patch.
Extension: https://github.com/riscv/riscv-zacas
Ratification: https://jira.riscv.org/browse/RVS-68
On 7/26/24 1:18 PM, Philipp Tomsich wrote:
Nitpick: a typo slipped into the comment — "regsiter" -> "register".
Thanks. The pre-commit tester also pointed out a couple formatting
nits. I'll fix both.
Jeff
GCC developers:
Version 2, updated rs6000-overload.def to remove adding additonal
internal names and to change XXSLDWI_Q to XXSLDWI_1TI per comments from
Kewen. Move new documentation statement for the PIVPR built-ins per
comments from Kewen. Updated dg-do-run directive and added comment
ab
On 7/26/24 2:42 PM, Robin Dapp wrote:
Hi,
when the source mode is potentially larger than one vector (e.g. an
LMUL2 mode for VLEN=128) we don't know which vector the subreg actually
refers to. For zvl128b and LMUL=2 the subreg in (subreg:V2DI (reg:V4DI))
could actually be the a full (high) v
GCC maintainers:
Per a report from a user, the existing vec_test_lsbb_all_ones and,
vec_test_lsbb_all_zeros built-ins are not documented in the GCC
documentation file.
The following patch adds missing documentation for the
vec_test_lsbb_all_ones and, vec_test_lsbb_all_zeros built-ins.
Plea
GCC maintainers:
This patch adds a comment to the VEC_IC definitions to clarify the V1TI
"TARGET_POWER10" mode per the request by Segher in the feedback to patch
"https://gcc.gnu.org/pipermail/gcc-patches/2024-July/658156.html";.
https://gcc.gnu.org/pipermail/gcc-patches/2024-July/658156.html
This patch extends our SARIF output to capture relationships between
locations within a result (§3.34). In particular, this captures
chains of #includes relating to diagnostics and to events within
diagnostic paths.
For example, consider:
include-chain-1.c:
#include "include-chain-1.h"
inclu
On Fri, Jul 26, 2024 at 01:17:57PM -0400, Jason Merrill wrote:
> On 7/26/24 12:52 AM, Nathaniel Shead wrote:
> > On Tue, Jul 23, 2024 at 04:17:22PM -0400, Jason Merrill wrote:
> > > On 6/15/24 10:29 PM, Nathaniel Shead wrote:
> > > > Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
While working on isel, I found that the current way of doing current_properties
in function can easily make a mistake and having to do stuff like `(a & b ) ==
0`
and `a |= b;` and `a &= ~b;` is not so obvious what was going on.
So let's add a few helper methods to function:
* set_property
* unset_
> OK.
Committed, thanks Richard.
Pan
-Original Message-
From: Richard Biener
Sent: Friday, July 26, 2024 9:32 PM
To: Li, Pan2
Cc: gcc-patches@gcc.gnu.org; juzhe.zh...@rivai.ai; kito.ch...@gmail.com;
tamar.christ...@arm.com; jeffreya...@gmail.com; rdapp@gmail.com
Subject: Re: [PAT
101 - 123 of 123 matches
Mail list logo
