libstdc++-v3/ChangeLog:
* include/std/queue (formatter, _CharT>)
(formatter, _CharT>):
Add _GLIBCXX_RESOLVE_LIB_DEFECTS comments.
---
I would send this as committed, but realized, that there is hight change
of there being a type somewhere.
libstdc++-v3/include/std/queue |
Before the change in g:309dbcea2cabb31bde1a65cdfd30bb7f87b170a2 we would never
set a range for constant VF and requires partial vector loops.
I think a range could be set, since I think the number of latch executions is a
ceiling division of TYPE_MAX_VALUE / vf. To account for the partial iteratio
This was merged. Thanks for working on it.
However, the constant_wrapper paper accepted in Sofia, modifies the concept:
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p2781r8.html
On Tue, Jul 8, 2025 at 1:01 PM Tomasz Kaminski wrote:
> Maybe adding a negative test for the error when c
Ok for trunk and releases/gcc-15?
--
The scheduler allows the `and` instruction to be placed at 3 different
locations. Update the function body to contain all 3 locations.
Also, armv8.1-m.main can use `ldr` instead of `pop` to return.
gcc/testsuite/ChangeLog:
* gcc.target/arm/unsigned-e
zvfh is not enabled at the testsuite level. It has to be enabled on a testcase
by testcase basis. This was correctly done for compile tests but not for run
tests. This patch fixes it.
Also, to ensure correct results with half-precision floats, MAX_RELATIVE_DIFF is
set according to the type.
gcc/te
Pushed to the gcc-15 branch today.
Thanks,
Arthur
On 4/29/25 9:20 AM, arthur.co...@embecosm.com wrote:
From: Arthur Cohen
Hi everyone,
We noticed inconsistent errors when running name-resolution 2.0 on
certain files, where an invalid error was triggered and the message was
from the `funny_i
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
While working on Reflection I noticed that we reject:
union U { int i; };
constexpr auto r = ^^typename ::U;
which is due to PR83469. Andrew P. posted a patch in 2021:
https://gcc.gnu.org/pipermail/gcc-patches/2021-Decemb
On Thu, Jul 3, 2025 at 12:38 PM Luc Grosheintz
wrote:
> This commit completes the implementation of P2897R7 by implementing and
> testing the template class aligned_accessor.
>
> libstdc++-v3/ChangeLog:
>
> * include/bits/version.def (aligned_accessor): Add.
> * include/bits/versi
Kyrylo Tkachov writes:
> Thanks for your comments, do you mean something like the following?
Yeah, the patch LGTM, thanks.
Richard
> Or do you mean to have separate alternatives with each one individually tying
> one of operands 2 or 3 to r0?
>
> Kyrill
>
>
>>
>> Thanks,
>> Tamar
>>
>>> Than
On 6/19/25 8:13 AM, Jakub Jelinek wrote:
Hi!
The following patch implements the constexpr structured bindings part of
the P2686R4 paper, so the [dcl.pre], [dcl.struct.bind], [dcl.constinit]
and first hunk in [dcl.constexpr] changes.
The paper doesn't have a feature test macro and the constexpr s
Ah sorry, a problem of last minute change.
I'll fix it if not done already.
On 08/07/2025 13:55, Jonathan Wakely wrote:
On Mon, 7 Jul 2025 at 11:12, Jonathan Wakely wrote:
On Sat, 5 Jul 2025 at 14:03, François Dumont wrote:
On 01/07/2025 22:51, Jonathan Wakely wrote:
On Mon, 16 Jun 2025 at
This patch implements _Escaping_sink, that stores characters in the
local (stack) buffer, and when filled escapes the range to underlying
sink.
To support that we define __write_escaped_unicode_part functions, that
takes the __str and __prev_esc by reference. The __prev_esc value is
updated based
Hi!
On Tue, Jul 08, 2025 at 08:51:30AM +, Cui, Lili wrote:
> > rs6000 does not *have* a hard frame pointer!
>
> Oh, I see. The handling of HARD_FRAME_POINTER_REGNUM seems redundant for
> rs6000.
The Power Architecture, Power ISA, nor any of our ABIs has a frame
pointer. GCC generic code r
On 7/8/25 6:21 AM, Robin Dapp wrote:
Hi,
in emit_vlmax_insn_lra we use a vsetivli for an immediate AVL.
XTHeadVector does not support this, so guard appropriately.
Regtested on rv64gcv_zvl512b.
Regards
Robin
PR target/120461
gcc/ChangeLog:
* config/riscv/riscv-v.cc (emit_vlmax_
On 7/8/25 6:21 AM, Robin Dapp wrote:
Hi,
if a user passes a string that doesn't represent a variable we still try
to compute a hash for its type. Its tree does not represent a type but
just an exceptional, though. This patch just ignores it, leaving the
error to the checking code later.
Re
Hi,
if a user passes a string that doesn't represent a variable we still try
to compute a hash for its type. Its tree does not represent a type but
just an exceptional, though. This patch just ignores it, leaving the
error to the checking code later.
Regtested on rv64gcv_zvl512b.
Regards
Rob
Hi,
in emit_vlmax_insn_lra we use a vsetivli for an immediate AVL.
XTHeadVector does not support this, so guard appropriately.
Regtested on rv64gcv_zvl512b.
Regards
Robin
PR target/120461
gcc/ChangeLog:
* config/riscv/riscv-v.cc (emit_vlmax_insn_lra): Do not emit
vset
On 7/8/25 9:44 AM, Richard Biener wrote:
On Tue, Jul 8, 2025 at 3:25 PM Jason Merrill wrote:
On 7/8/25 4:35 AM, Richard Biener wrote:
On Mon, Jul 7, 2025 at 11:33 PM H.J. Lu wrote:
On Tue, Jul 8, 2025 at 5:02 AM H.J. Lu wrote:
On Mon, Jul 7, 2025 at 11:08 PM Jason Merrill wrote:
On 7
On Tue, Jul 8, 2025 at 2:48 PM Jonathan Wakely wrote:
> On Tue, 8 Jul 2025 at 13:31, Tomasz Kaminski wrote:
> >
> >
> >
> > On Sat, Jul 5, 2025 at 1:12 AM Jonathan Wakely
> wrote:
> >>
> >> For allocations with size > alignment and size % alignment != 0 we were
> >> sometimes returning pointers
On Tue, 8 Jul 2025, Tamar Christina wrote:
> Before the change in g:309dbcea2cabb31bde1a65cdfd30bb7f87b170a2 we would never
> set a range for constant VF and requires partial vector loops.
>
> I think a range could be set, since I think the number of latch executions is
> a
> ceiling division of
On Tue, 8 Jul 2025, Tamar Christina wrote:
> This patch adds support for niters ranges for partial
> vector loops.
>
> Due to the last iteration being partial the bounds should
> be at least 1 but niters // vf as the max.
>
> Bootstrapped Regtested on aarch64-none-linux-gnu,
> arm-none-linux-gnu
On Tue, 8 Jul 2025 at 13:31, Tomasz Kaminski wrote:
>
>
>
> On Sat, Jul 5, 2025 at 1:12 AM Jonathan Wakely wrote:
>>
>> For allocations with size > alignment and size % alignment != 0 we were
>> sometimes returning pointers that did not meet the requested aligment.
>> For example, allocate(24, 16
There is already $(CFLAGS-$@) to add extra flags for a particular
target. This could easily be extended by adding $(CFLAGS-$(@D)) to add
flags for all targets in a directory.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"An
On 5/30/25 11:22 PM, Nathaniel Shead wrote:
On Fri, May 30, 2025 at 11:10:08AM -0400, Patrick Palka wrote:
On Fri, 30 May 2025, Patrick Palka wrote:
On Fri, 30 May 2025, Nathaniel Shead wrote:
On Wed, May 28, 2025 at 02:14:06PM -0400, Patrick Palka wrote:
On Tue, 27 May 2025, Nathaniel Shea
On Tue, 8 Jul 2025 at 17:17, Torbjörn SVENSSON
wrote:
>
> Ok for trunk and releases/gcc-15?
>
> --
>
> The scheduler allows the `and` instruction to be placed at 3 different
> locations. Update the function body to contain all 3 locations.
> Also, armv8.1-m.main can use `ldr` instead of `pop` to r
On Tue, Jul 8, 2025 at 3:24 PM Jonathan Wakely wrote:
> On Tue, 8 Jul 2025 at 14:12, Tomasz Kaminski wrote:
> >
> >
> >
> > On Tue, Jul 8, 2025 at 2:48 PM Jonathan Wakely
> wrote:
> >>
> >> On Tue, 8 Jul 2025 at 13:31, Tomasz Kaminski
> wrote:
> >> >
> >> >
> >> >
> >> > On Sat, Jul 5, 2025 at
On 7/8/25 5:08 AM, Andreas Schwab wrote:
gcc:
PR target/120995
* config/riscv/sync.md (zacas_atomic_cas_value_strong):
Allow op3 to be zero.
gcc/testsuite:
PR target/120995
* gcc.target/riscv/amo/zabha-zacas-atomic-cas.c: New test.
Thanks. I didn't se
> On 8 Jul 2025, at 12:39, Tamar Christina wrote:
>
>> -Original Message-
>> From: Richard Sandiford
>> Sent: Tuesday, July 8, 2025 10:07 AM
>> To: Tamar Christina
>> Cc: Kyrylo Tkachov ; GCC Patches > patc...@gcc.gnu.org>; Richard Earnshaw ; Alex
>> Coplan ; Andrew Pinski
>> Subject
On Sat, Jul 5, 2025 at 1:12 AM Jonathan Wakely wrote:
> For allocations with size > alignment and size % alignment != 0 we were
> sometimes returning pointers that did not meet the requested aligment.
> For example, allocate(24, 16) would select the pool for 24-byte objects
> and the second alloc
> -Original Message-
> From: Andreas Schwab
> Sent: Tuesday, July 8, 2025 03:16
> To: Robert Dubner
> Cc: Rainer Orth ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> On Jul 07 2025, Robert Dubner wrote:
>
> > Furthermore, even if this method did
All patches were merged. I will double check that we got all the papers
listed and the issue, and close it.
Thanks again for your submissions.
On Tue, Jul 8, 2025 at 10:26 AM Luc Grosheintz
wrote:
> Patches 1/5 ... 4/5 aren't sent because corresponding commits from v3
> should be used. The chang
On Tue, Jul 8, 2025 at 3:25 PM Jason Merrill wrote:
>
> On 7/8/25 4:35 AM, Richard Biener wrote:
> > On Mon, Jul 7, 2025 at 11:33 PM H.J. Lu wrote:
> >>
> >> On Tue, Jul 8, 2025 at 5:02 AM H.J. Lu wrote:
> >>>
> >>> On Mon, Jul 7, 2025 at 11:08 PM Jason Merrill wrote:
>
> On 7/1/25 5:
On 7/7/25 9:48 PM, Li, Pan2 wrote:
Is that correct? Don't you need to be testing that the platform has
vector in addition to being rv64?
It is riscv.exp test, so I think vector extension is not required here.
Oh, I see. We're not actually turning on RVV anywhere. OK for the trunk.
It lo
On 27/05/2025 07:33, Christophe Lyon wrote:
> On Mon, 26 May 2025 at 18:14, Christophe Lyon
> wrote:
>>
>> Remove #pragma GCC target ("arch=armv8.2-a+bf16") and preceding
>> target and is thus useless.
> I guess this should read:
> Remove #pragma GCC target ("arch=armv8.2-a+bf16") since it matches
On 7/8/2025 2:03 AM, Steve Kargl wrote:
On Sun, Jul 06, 2025 at 09:09:53PM +0800, Yuao Ma wrote:
Hi Tobias,
On 7/6/2025 6:34 PM, Tobias Burnus wrote:
As that commit is from 2020 and 2.69 in from 2012, it seems as if your
autoconf is too new. Can you re-check that the right version is at the
On 7/7/25 4:52 PM, Marek Polacek wrote:
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
This patch is an attempt to implement P2036R3 along with P2579R0, fixing
build breakages caused by P2036R3.
The simplest example is:
auto counter1 = [j=0]() mutable -> decltype(j) {
On 7/8/25 11:32 AM, Marek Polacek wrote:
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
While working on Reflection I noticed that we reject:
union U { int i; };
constexpr auto r = ^^typename ::U;
which is due to PR83469. Andrew P. posted a patch in 2021:
https://
On 7/8/25 17:11, Tomasz Kaminski wrote:
This was merged. Thanks for working on it.
However, the constant_wrapper paper accepted in Sofia, modifies the concept:
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p2781r8.html
Interesting! I'll go hiking for 3 days, then I'll look at thi
On 6/9/25 9:00 PM, Jeremy Rifkin wrote:
Hi,
This fixes PR c/82134 which concerns gcc emitting an incorrect unused
result diagnostic for empty types. This diagnostic is emitted from
tree-cfg.cc because of a couple code paths which attempt to avoid
copying empty types, resulting in GIMPLE that isn'
On Tue, Jul 8, 2025 at 6:18 PM Luc Grosheintz
wrote:
>
>
> On 7/8/25 17:11, Tomasz Kaminski wrote:
> > This was merged. Thanks for working on it.
> >
> > However, the constant_wrapper paper accepted in Sofia, modifies the
> concept:
> > https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p27
On 5/23/25 9:00 PM, Nathaniel Shead wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk/15?
-- >8 --
When emitting a primary module interface, we must re-stream any TU-local
entities that we saw in a partition. This patch adds the missing
members from core_vals.
As a drive-
BUMP
On Thu, Jul 3, 2025 at 12:36 PM Luc Grosheintz
wrote:
> This commit implements and tests the function is_sufficiently_aligned
> from P2897R7.
>
> libstdc++-v3/ChangeLog:
>
> * include/bits/align.h (is_sufficiently_aligned): New function.
> * include/bits/version.def (is_sufficient
On Thu, Jul 3, 2025 at 12:36 PM Luc Grosheintz
wrote:
> All test code of default_accessor can be reused. This commit moves
> the reuseable code into a file generic.cc and prepares the tests for
> reuse with aligned_accessor.
>
> The AllocatorTrait creates a unified interface for creating both
> d
Hi,
> On Jul 8, 2025, at 01:18, Jakub Jelinek wrote:
>>
>>>5th argument ACCESS_MODE:
>>> -1: Unknown access semantics
>>> 0: none
>>> 1: read_only
>>> 2: write_only
>>> 3: read_write
>>>6th argument: A constant 0 with the pointer TYPE to the original flexible
>>>
Matthieu Longo writes:
> Those methods's implementation is relying on duck-typing at compile
> time.
> The structure corresponding to the node of a doubly linked list needs
> to define attributes 'prev' and 'next' which are pointers on the type
> of a node.
> The structure wrapping the nodes and o
> -Original Message-
> From: Richard Biener
> Sent: Tuesday, July 8, 2025 09:54
> To: Robert Dubner
> Cc: Andreas Schwab ; Rainer Orth bielefeld.de>; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> On Tue, Jul 8, 2025 at 3:45 PM Robert Dubner wrot
On Tue, Jul 8, 2025 at 12:46 AM Robert Dubner wrote:
>
>
>
> > -Original Message-
> > From: Rainer Orth
> > Sent: Monday, July 7, 2025 18:08
> > To: Robert Dubner
> > Cc: gcc-patches@gcc.gnu.org
> > Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
> >
> > Hi Robert,
> >
> > > I
This patch extends the splitting patterns for combining FP comparisons
with predicated logical operations such that they cover all of SVE_F.
gcc/ChangeLog:
* config/aarch64/aarch64-sve.md (*fcm_and_combine):
Extend from SVE_FULL_F to SVE_F.
(*fcmuo_and_combine): Likewise.
Hi all,
I'd like to commit this instead of the OK'd patch 05/14 from the
unpacked FP series [1], as I later realised that:
* I can use the existing unpacked_fcm_1.c file to test these
splitting patterns, since the stores to out[i] are conditional
on the comparison result a
This libgo patch avoids the libc memmove and memclr functions when the
type being moved or cleared may contain pointer values. This is
necessary to ensure that Go's concurrent garbage collector doesn't see
corrupt pointer values.
The libc memmove and memclr don't reliably operate on full memory
wo
> It looks like there's ~200 uses of risc_v in dg-do run clauses in the
> "sat" subdirectory tests. Should those be adjusted as well?
Yes, I will take care of that soon.
Pan
-Original Message-
From: Jeff Law
Sent: Tuesday, July 8, 2025 9:47 PM
To: Li, Pan2 ; gcc-patches@gcc.gnu.org
C
On 6/6/25 9:17 AM, Jakub Jelinek wrote:
On Wed, Jun 04, 2025 at 02:03:17PM +0200, Jakub Jelinek wrote:
You mean also check TREE_NOTHROW (fndecl) which we currently propagate
conservatively (if we can prove something never throws, we set it)
or something else?
If TREE_NOTHROW, that would be twice
Bootstrapped and regtested on aarch64-linux-gnu, loongarch64-linux-gnu,
and x86_64-linux-gnu. Ok for trunk?
Xi Ruoyao (2):
testsuite: Enable the PR 87600 tests for LoongArch
lra: Reallow reloading user hard registers if the insn is not asm [PR
120983]
gcc/lra-constraints.cc |
I'm going to refine a part of the PR 87600 fix which seems triggering
PR 120983 that LoongArch is particularly suffering. Enable the PR 87600
tests so I'll not regress PR 87600.
gcc/testsuite/ChangeLog:
PR rtl-optimization/87600
PR rtl-optimization/120983
* gcc.dg/pr87600
* config/abi/post/x86_64-linux-gnu/x32/baseline_symbols.txt:
Updated.
--
H.J.
From 98d20df2accfa045f1ad694b0b0d94855d7a75f3 Mon Sep 17 00:00:00 2001
From: "H.J. Lu"
Date: Wed, 9 Jul 2025 09:43:52 +0800
Subject: [PATCH] libstdc++: Update some baseline_symbols.txt (x32)
* config/abi/post/x86_64
The PR 87600 fix has disallowed reloading user hard registers to resolve
earlyclobber-induced conflict.
However before reload, recog completely ignores the constraints of
insns, so the RTL passes may produce insns where some user hard
registers violate an earlyclobber. Then we'll get an ICE witho
Am 05.07.25 um 14:55 schrieb Mikael Morin:
Hello Andre,
I get a regression on this testcase with a patch that is otherwise
regression-free.
I think the testcase is invalid.
It does:
type(container), allocatable :: list(:)
list = [list, new_elem(5)]
so it's using the variable 'list
> -Original Message-
> From: James K. Lowden
> Sent: Tuesday, July 8, 2025 17:11
> To: Robert Dubner
> Cc: Richard Biener ; Rainer Orth
> ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> On Tue, 8 Jul 2025 14:11:19 -0500 (CDT)
> Robert Dubner
Hi Piyush,
On 7/3/25 06:32, Piyush Raj wrote:
> This patch adds the bpf-vmtest-tool subdirectory under contrib which tests
> BPF programs under a live kernel using a QEMU VM. It automatically
> builds the specified kernel version with eBPF support enabled
> and stores it under "~/.bpf-vmtest-tool
This libgo patch passe the correct pointer to the system call in
recvmsgRaw. The code in recvmsgRaw, introduced in CL 384695
(https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590289.html),
incorrectly passed &rsa to the recvmsg system call. But in recvmsgRaw
rsa is already a pointer passed b
AVL propagation currently assumes that it can propagate a constant AVL
into any vector insn and trips an assert if the insn fails to recognize
after such a propagation.
However, for xtheadvector that is not a correct assumption; xtheadvector
does not allow the vector length to be a constant
Uros Bizjak writes:
> On Thu, Jul 3, 2025 at 12:01 PM H.J. Lu wrote:
>>
>> When profiling is enabled with shrink wrapping, the mcount call may not
>> be placed at the function entry after
>>
>> pushq %rbp
>> movq %rsp,%rbp
>>
>> As the result, the profile data may be skewed which makes PGO less
> On Jul 8, 2025, at 17:46, Siddhesh Poyarekar wrote:
>
> On 2025-07-08 17:17, Qing Zhao wrote:
>> Are the above the correct and efficient updates to the .ACCESS_WITH_SIZE to
>> resolve both PR121000 and the issue
>> we have with counted_by for pointers?
>
> I don't know about PR121000, but f
101 - 164 of 164 matches
Mail list logo
