On Thu, Apr 10, 2025 at 10:10 PM Richard Sandiford
wrote:
>
> PR119610 is about incorrect CFI output for a stack probe when that
> probe is not the initial allocation. The main aarch64 stack probe
> function, aarch64_allocate_and_probe_stack_space, implicitly assumed
> that the incoming stack poi
On Fri, Apr 11, 2025 at 1:32 AM Jonathan Wakely wrote:
> This is the last piece of P1206R7, adding new members to
> std::basic_string.
>
> libstdc++-v3/ChangeLog:
>
> PR libstdc++/111055
> * include/bits/basic_string.h (_S_copy_range): New function.
> (basic_string(from_ra
On Thu, Apr 10, 2025 at 10:47 PM Jonathan Wakely wrote:
> On 10/04/25 22:36 +0200, François Dumont wrote:
> >After running the test with -fno-exceptions option we rather need this
> >patch.
> >
> >Ok to commit ?
> >
> >François
> >
> >
> >On 10/04/2025 21:08, François Dumont wrote:
> >>Hi
> >>
>
Hello!
I would like to backport PR115568 and PR119689 to release branches.
Author: Richard Biener
Date: Wed Apr 9 14:36:19 2025 +0200
rtl-optimization/119689 - compare-debug failure with LRA
The previous change to fix LRA rematerialization broke compare-debug
for i586 bootstrap. Fi
> On 10 Apr 2025, at 19:31, Richard Biener wrote:
>
> External email: Use caution opening links or attachments
>
>
>> Am 10.04.2025 um 17:27 schrieb Jennifer Schmitz :
>>
>> This patch adds a test case to the testsuite for PR119706.
>> The bug was already fixed by
>> https://gcc.gnu.org/pip
On Thu, 10 Apr 2025, Jakub Jelinek wrote:
> Hi!
>
> The following testcase is miscompiled I believe starting with
> PR112941 r14-6742. That commit fixed the bitint-55.c testcase.
> The m_first initialization for such conversion initializes 2 SSA_NAMEs,
> one is PHI result on the loop (m_data[sav
P8700 is a high-performance processor from MIPS by extending RISCV with the
MIPS custom instructions.
Tested with dejagnu riscv.exp tests for --mtune=mips-p8700.
Please refer @ https://mips.com/products/hardware/p8700/
---
gcc/ChangeLog| 21 +++
gcc/common/confi
Codegen is incorrectly emitting a ".p2align 3" that coerces the
alignment of the .note.gnu.property section from 4 to 8 on rv32.
2025-04-11 Jesse Huang
gcc/ChangeLog
* config/riscv/riscv.cc (riscv_file_end): Fix .p2align value.
gcc/testsuite/ChangeLog
* gcc.target/riscv/gnu-
gcc/ChangeLog
PR tree-optimization/87909
* common.opt.urls: Regenerate.
* doc/invoke.texi (Option Summary): Add -ftree-cselim.
(Optimize Options): Likewise.
---
gcc/common.opt.urls | 3 +++
gcc/doc/invoke.texi | 10 --
2 files changed, 11 insertions(+), 2 d
On 4/9/25 2:35 PM, Jonathan Yong wrote:
Attached patch OK for master branch? Gcc produced struct sizes match
those of MSVC when __ms_struct__ is used, both producing a layout size
of 12.
Will push soon if there are no objections.
Pushed to master branch.
On 4/9/25 2:27 PM, Jonathan Yong wrote:
Attached patch OK for master branch?
Will push soon if there are no objections.
Pushed to master branch.
gcc/ChangeLog
PR middle-end/14708
* doc/invoke.texi (Optimize Options): List -fexcess-precision
before -ffloat-store, moving some background discussion to the
former from the latter. Recommend using -fexcess-precision=standard
instead of -ffloat-store.
---
Vishnu Mohandas writes:
> Hello,
Hi,
> The patch below proposes a possible improvement for the issue mentioned in
> bug 65445. Although I'm not certain that it
> address all the concerns, it does seem to make it better.>
Unfortunately, I see a few issues here. There needs to be a ChangeLog
en
A target using 16-bit ints won't have enough bits to hold the whole
flag_sanitize set. Be explicit about using uint32 for the attribute data.
Signed-off-by: Keith Packard
---
gcc/c-family/c-attribs.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/c-family/c-attribs.
From: Philip Herron
We dont need to assert here the lifetime code already supports this case.
Fixes Rust-GCC#3657
gcc/rust/ChangeLog:
* typecheck/rust-hir-type-check-base.cc: remove assertion
gcc/testsuite/ChangeLog:
* rust/compile/issue-3657.rs: New test.
Signed-off-by: Phi
This is the last piece of P1206R7, adding new members to
std::basic_string.
libstdc++-v3/ChangeLog:
PR libstdc++/111055
* include/bits/basic_string.h (_S_copy_range): New function.
(basic_string(from_range_t, R%%, const Alloc&)): New
constructor.
(append_ra
> On Apr 8, 2025, at 13:13, Siddhesh Poyarekar wrote:
>
> On 2025-04-08 12:41, Qing Zhao wrote:
>> For the following small example:
>> [ counted_by_whole]$ cat t.c
>> #include
>> #include
>> struct annotated {
>> size_t count;
>> char other;
>> char array[] __attribute__((counted_by (co
On 4/7/25 1:57 AM, Richard Sandiford wrote:
Sam James writes:
Richard Sandiford writes:
This series is an update of:
https://gcc.gnu.org/pipermail/gcc-patches/2025-April/679924.html
As discussed in that thread, the changes since last time are to make
distribute_links start from the l
Hi,
These are the patches for fixing PR109071 for GCC16 stage1:
Adding -fdiagnotics-details into GCC to provide more hints to the
end users on how the warnings come from, in order to help the user
to locate the exact location in source code on the specific warnings
due to compiler optimizations.
On 2025-04-10 01:41, Martin Uecker wrote:
I have some questions about this: The access would add new reads
to the size field. For counted_by, so far, those are somehow
coupled to the access to the member. From this you would assume
For the currently implemented subset, updates to the storage
On Sun, Apr 06, 2025 at 09:02:07AM +0100, Iain Sandoe wrote:
>
> +
> +#if !defined (HAVE_STRTOF128)
> +# if USE_QUADMATH
> +# define strtof128 strtoflt128
> +# else
> +# error "no available string to float 128"
> +# endif
> +#endif
If there is no strtof128 and not using libquadmath, there is a
On Tue, Apr 08, 2025 at 11:57:46AM +0200, Tobias Burnus wrote:
> libgomp/ChangeLog:
>
> * Makefile.am (%.mod): Add -Wno-c-binding-type.
> * Makefile.in: Regenerate.
LGTM.
Jakub
Uses the FTM infrastructure to create an internal feature testing macro
for partial availability of mdspan; which is then used to hide the
contents of the header mdspan when compiling against a standard prior to
C++23.
libstdc++-v3/ChangeLog:
* include/bits/version.def: Add internal featu
On Mon, 7 Apr 2025 at 09:08, Thomas Schwinge wrote:
>
> Hi!
>
> On 2025-03-14T11:39:20+0100, I wrote:
> > As the first of a few patches to enable libstdc++ for GCN, nvptx targets,
> > [...]
>
> > some more fine-tuning is to follow later on.)
>
> Any comments before I push the attached
> "GCN, nvpt
> On 26 Mar 2025, at 08:42, Kyrylo Tkachov wrote:
>
> Ping.
Ping.
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/676958.html
I’ve ran a profiled LTO bootstrap of GCC with the new bootstrap-lto-locality
bootstrap config
And compared it against a GCC produced by the existing lto-bootstra
On Thu, Apr 10, 2025 at 07:21:23PM +0100, Iain Sandoe wrote:
> > So, here is an updated patch based on your patch, so far briefly
> > tested on x86_64 with recent glibc (i.e. with the *f128 APIs).
>
> makes sense to me - and builds and tests on x86_64-darwin (which needs
> libquadmath) without iss
On Thu, Apr 10, 2025 at 10:32:57AM +0100, Richard Sandiford wrote:
> In r10-4803-g8489e1f45b50600c I'd used POINTER_DIFF_EXPR to subtract
> the two pointers involved in an overlap test. I'm not sure whether
> I'd specifically chosen that over MINUS_EXPR or not; if so, the only
> reason I can think
[1] https://github.com/riscv/riscv-zalasr
Add minimal support for the zalasr (load-acquire/store-release)
extension
Currently there is no toggle to opt into the abi-breaking note 3
mappings in the PSABI doc so support for that has been omitted from this
patch.
gcc/ChangeLog:
* common/co
From: Philip Herron
We hit assertions on empty enum or unknown variant, this catches the error
and emits a new diagnostic.
Fixes Rust-GCC#3656
gcc/rust/ChangeLog:
* typecheck/rust-hir-type-check-pattern.cc (TypeCheckPattern::visit):
emit error
gcc/testsuite/ChangeLog:
* rust
From: Ard Biesheuvel
Commit bde21de1205 ("i386: Honour -mdirect-extern-access when calling
__fentry__") updated the logic that emits mcount() / __fentry__() calls
into function prologues when profiling is enabled, to avoid GOT-based
indirect calls when a direct call would suffice.
There are two
On Mon, Apr 07, 2025 at 09:30:59AM +0200, Richard Biener wrote:
> On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote:
> > My question stands on integrating COBOLworx' UAT as-is for now
> > (Copyright is all on FSF; built automatically [it is autoconf, which is
> > a requirement for VCS checkouts],
On Thu, Apr 10, 2025 at 1:21 PM Tomasz Kaminski wrote:
>
>
> On Wed, Apr 9, 2025 at 9:28 AM Luc Grosheintz
> wrote:
>
>> This implements std::extents from according to N4950 and
>> contains partial progress towards PR107761.
>>
>> If an extent changes its type, there's a precondition in the sta
On Thu, Apr 10, 2025 at 12:19:57PM -0400, Jason Merrill wrote:
> On 4/10/25 8:46 AM, Nathaniel Shead wrote:
> > Regression raised with my by private correspondance.
> > Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
> >
> > -- >8 --
> >
> > My change in r15-9216 broke the case w
diff --git
a/libstdc++-v3/testsuite/23_containers/mdspan/extents/assign_copy_01_neg.cc
b/libstdc++-v3/testsuite/23_containers/mdspan/extents/assign_copy_01_neg.cc
new file mode 100644
index 000..8a514f2207b
--- /dev/null
+++ b/libstdc++-v3/testsuite/23_containers/mdspan/extents/assign_co
libbacktrace/ChangeLog:
* atomic.c (backtrace_atomic_store_int): Use int for old value.
---
Ian approved this when I submitted a pull request to the libbacktrace
github repo.
Tested x86_64-linux. Pushed to trunk.
libbacktrace/atomic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
Jakub Jelinek writes:
> On Sun, Apr 06, 2025 at 09:02:07AM +0100, Iain Sandoe wrote:
>>
>> +
>> +#if !defined (HAVE_STRTOF128)
>> +# if USE_QUADMATH
>> +# define strtof128 strtoflt128
>> +# else
>> +# error "no available string to float 128"
>> +# endif
>> +#endif
>
> If there is no strtof128
On Wed, 9 Apr 2025 at 09:12, Uros Bizjak wrote:
>
> On Tue, Apr 8, 2025 at 6:59 PM Ard Biesheuvel wrote:
> >
> > On Tue, 8 Apr 2025 at 18:44, H.J. Lu wrote:
> > >
> > > On Tue, Apr 8, 2025 at 9:39 AM Ard Biesheuvel wrote:
> > > >
> > > > On Tue, 8 Apr 2025 at 15:33, H.J. Lu wrote:
> > > > >
>
Whoops, attached wrong patch to last message. This is the right patch.
Trivial fallout from the recent combine work. We end up with a srai
rather than an xor in some of the saturation sequences. Both variants
look equally performant, so I'm just adjusting the expected test output.
Pushing
---
Pushed.
htdocs/gcc-3.2/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-3.2/changes.html b/htdocs/gcc-3.2/changes.html
index 7b9ea63f..4ab9fdce 100644
--- a/htdocs/gcc-3.2/changes.html
+++ b/htdocs/gcc-3.2/changes.html
@@ -59,7 +59,7 @@
C++
-
Tested x86_64-pc-linux-gnu, applying to trunk and 14.
-- 8< --
Value-initialization built an AGGR_INIT_EXPR to set AGGR_INIT_ZERO_FIRST on.
Passing that AGGR_INIT_EXPR to maybe_constant_value returned a TARGET_EXPR,
which potential_constant_expression_1 mistook for a temporary.
We shouldn't add
Hi!
The following testcase is miscompiled I believe starting with
PR112941 r14-6742. That commit fixed the bitint-55.c testcase.
The m_first initialization for such conversion initializes 2 SSA_NAMEs,
one is PHI result on the loop (m_data[save_data_cnt]) and the other
(m_data[save_data_cnt+1]) is
On 10/04/25 22:36 +0200, François Dumont wrote:
After running the test with -fno-exceptions option we rather need this
patch.
Ok to commit ?
François
On 10/04/2025 21:08, François Dumont wrote:
Hi
No problem detected now that we really test std::deque
shrink_to_fit implementation.
On 9/6/24 7:15 AM, Simon Martin wrote:
We ICE upon the following *valid* code when mangling the requires
clause
=== cut here ===
template struct s1 {
enum { e1 = 1 };
};
template struct s2 {
enum { e1 = s1::e1 };
s2() requires(0 != e1) {}
};
s2<8> a;
=== cut here ===
The problem is t
After running the test with -fno-exceptions option we rather need this
patch.
Ok to commit ?
François
On 10/04/2025 21:08, François Dumont wrote:
Hi
No problem detected now that we really test std::deque
shrink_to_fit implementation.
libstdc++: Add std::deque<>::shrink_to_fit tes
Hi!
As noted by Richi on a large testcase, there are unnecessary paddings
in some heavily used dwarf2out.{h,cc} structures on 64-bit hosts.
struct dw_val_node {
enum dw_val_class val_class;/* 0 4 */
/* XXX 4 bytes hole, try to pack */
struct
From: Pierre-Emmanuel Patry
These constructor for eroneous state are not in use anymore since we
replaced this error state with an optional in the parent nodes.
gcc/rust/ChangeLog:
* ast/rust-expr.h: Remove error getter and constructor.
Signed-off-by: Pierre-Emmanuel Patry
---
gcc/ru
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
tsubst_stmt already registers a local capture proxy as a
local_specialization of both an outer capture proxy and the captured
variable; we also need to do that in add_extra_args.
PR c++/119345
gcc/cp/ChangeLog:
* pt.cc (ad
Hi Iain,
>> On 9 Apr 2025, at 09:00, Rainer Orth wrote:
>>
>> Jakub Jelinek writes:
>>
>>> On Sun, Apr 06, 2025 at 09:02:07AM +0100, Iain Sandoe wrote:
+
+#if !defined (HAVE_STRTOF128)
+# if USE_QUADMATH
+# define strtof128 strtoflt128
+# else
+# error "no
On Mon, Apr 07, 2025 at 01:38:19PM -0400, Marek Polacek wrote:
> On Fri, Apr 04, 2025 at 08:56:40PM +0200, Jakub Jelinek wrote:
> > On Fri, Apr 04, 2025 at 08:52:10PM +0200, Richard Biener wrote:
> > > > Or do you want something further (like
> > > > switch (global_options.x_flag_cf_protection & ~C
> On Apr 10, 2025, at 15:22, Qing Zhao wrote:
>
>
>
>> On Apr 10, 2025, at 13:43, Martin Uecker wrote:
>>
>> Am Donnerstag, dem 10.04.2025 um 17:05 + schrieb Qing Zhao:
>>> Hi, Martin,
>>>
>>> Thanks a lot for all your comments and questions, really helpful.
>>>
>>>
>>
>> ...
Tejas Belagod writes:
> On 4/10/25 5:56 PM, Richard Sandiford wrote:
>> Tejas Belagod writes:
>>> Sorry, forgot to ask - Richard, are you happy for me to work on a
>>> separate patch to fix the test alongside your target +sve fix as a
>>> couple more functions (eg simd_reduction () and inscan.. (
PR119610 is about incorrect CFI output for a stack probe when that
probe is not the initial allocation. The main aarch64 stack probe
function, aarch64_allocate_and_probe_stack_space, implicitly assumed
that the incoming stack pointer pointed to the top of the frame,
and thus held the CFA.
aarch64
Hello,
The patch below proposes a possible improvement for the issue mentioned in
bug 65445. Although I'm not certain that it address all the concerns, it
does seem to make it better.
Bootstrapped on x86_64 Linux.
Thanks,
Vishnu
1 │ diff --git a/gcc/opt-functions.awk b/gcc/opt-functions.awk
Hi,
This reverts a change in the upstream D implementation of the compiler,
as the refactoring introduced a regression.
Bootstrapped and regression tested on x86_64-linux-gnu/-m32, and
committed to mainline.
Regards,
Iain.
---
gcc/d/ChangeLog:
* dmd/MERGE: Merge upstream dmd 51816cd01d
> On Apr 10, 2025, at 13:43, Martin Uecker wrote:
>
> Am Donnerstag, dem 10.04.2025 um 17:05 + schrieb Qing Zhao:
>> Hi, Martin,
>>
>> Thanks a lot for all your comments and questions, really helpful.
>>
>>
>
> ...
>>>
>>> An example I could imagine is when you memcpy
>>> the struct.
From: Pierre-Emmanuel Patry
gcc/rust/ChangeLog:
* resolve/rust-ast-resolve-expr.cc (ResolveExpr::visit):
Change error message to match rustc.
gcc/testsuite/ChangeLog:
* rust/compile/undeclared_label.rs: Change test
expected string.
Signed-off-by: Pierre-Emmanue
Hi
No problem detected now that we really test std::deque
shrink_to_fit implementation.
libstdc++: Add std::deque<>::shrink_to_fit test
The existing test is currently testing std::vector. Make it test
std::deque.
libstdc++-v3/ChangeLog:
* testsuite/23_container
> On 10 Apr 2025, at 17:36, Jakub Jelinek wrote:
>
> On Wed, Apr 09, 2025 at 02:22:16PM +0200, Rainer Orth wrote:
>>> Here is what I'm testing as an incremental fix, so far OK on x86_64-darwin
>>> and powerpcle64 (GLIBC 2.34) .. others in progress. Does it help the
>>> Solaris cases?
>>
>> I
On 4/9/25 4:13 PM, Jakub Jelinek wrote:
On Wed, Apr 09, 2025 at 04:01:49PM +0530, Tejas Belagod wrote:
It also looks like there might be a missing "+" in simd_reduction:
#pragma omp simd reduction (+:va, i)
for (j = 0; j < 16; j++)
va = svld1_s32 (svptrue_b32 (), a);
res = sv
From: Arthur Cohen
gcc/rust/ChangeLog:
* checks/errors/rust-feature.cc (Feature::create): Handle
`#![feature(min_specialization)]`.
* checks/errors/rust-feature.h: Likewise.
---
gcc/rust/checks/errors/rust-feature.cc | 4
gcc/rust/checks/errors/rust-feature.h | 1 +
2 fil
Hi,
Just a ping for
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/677635.html.
Thanks,
Konstantinos
> On Apr 7, 2025, at 22:15, Siddhesh Poyarekar wrote:
>
> On 2025-04-07 14:53, Qing Zhao wrote:
>>> Is there a reason to do this at the very end like this and not in the
>>> GIMPLE_ASSIGN case in the switch block? Something like this:
>>>
>>> tree rhs = gimple_assign_rhs1 (stmt);
>>>
> On 7 Apr 2025, at 13:24, Kyrylo Tkachov wrote:
>
>
>
>> On 7 Apr 2025, at 10:21, Tamar Christina wrote:
>>
>>> -Original Message-
>>> From: Kyrylo Tkachov
>>> Sent: Monday, March 31, 2025 1:43 PM
>>> To: i...@sandoe.co.uk
>>> Cc: Tamar Christina ; GCC Patches >> patc...@gcc.gnu.o
On Thu, 10 Apr 2025 at 18:53, Tomasz Kaminski wrote:
>
>
>
> On Thu, Apr 10, 2025 at 6:39 PM Jonathan Wakely wrote:
>> What happened to the changes to bits/version.def and bits/version.h ?
>>
>> I thought you were going to change version.def to use no_stdname but
>> now it's not in the patch at a
Hi,
Just a ping for
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/677788.html .
Thanks,
Konstantinos
Hi,
in categorize_ctor_elements_1 we do
VECTOR_CST_NELTS (value).to_constant ()
but VALUE's type can be a VLA vector (since r15-5780-g17b520a10cdaab).
This patch uses constant_lower_bound instead.
Bootstrapped and regtested on x86, aarch64, and power 10.
Regtested on rv64gcv_zvl512b.
Regards
A prior commit added std::extents, this commits adds the tests. The bulk
is focussed on testing the constructors. These are split into three
groups:
1. the ctor from other extents and the copy ctor,
2. the ctor from a pack of integer-like objects,
3. the ctor from shapes, i.e. span and array.
For
Hi Tejas,
On Tue, Apr 08, 2025 at 12:02:12PM +0530, Tejas Belagod wrote:
> On 4/7/25 3:33 PM, Jakub Jelinek wrote:
> >On Mon, Apr 07, 2025 at 03:28:29PM +0530, Tejas Belagod wrote:
> >>Add AArch64 SVE target exectute tests to test various workshare constructs
> >>and
> >>clauses with SVE types.
>
> This patch revisits the fix for PR 118097 and instead of deducing the
> necessary operation type it just uses the value collected and streamed
> by an earlier patch.
>
> It is bigger than the ones for propagating value ranges and known bits
> because we track constants both in parameters themsel
Tested with compilation of x86_64-linux -> riscv64-linux cross,
ok for trunk?
Yes.
--
Regards
Robin
The previous change to fix LRA rematerialization broke compare-debug
for i586 bootstrap. Fixed by using prev_nonnote_nondebug_insn
instead of prev_nonnote_insn.
Bootstrapped on i586-linux where the miscompare is gone with this
patch. Bootstrap and regtest running on x86_64-unknown-linux-gnu.
OK
On Wed, 9 Apr 2025 at 16:46, H.J. Lu wrote:
>
> On Wed, Apr 9, 2025 at 1:53 AM Ard Biesheuvel wrote:
> >
> > From: Ard Biesheuvel
> >
> > Commit bde21de1205 ("i386: Honour -mdirect-extern-access when calling
> > __fentry__") updated the logic that emits mcount() / __fentry__() calls
> > into fun
Attached patch OK for master branch?
Will push soon if there are no objections.
From 075f2ab502ca7291887c1fa75b5351fb0cbad013 Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10wa...@gmail.com>
Date: Wed, 9 Apr 2025 14:21:22 +
Subject: [PATCH] realloc-1.c: accept long long in warning for llp64
MI
Hi all,
this patch unifies handling of STAT= and ERRMSG= for some users of these
optional arguments. The first introduction of the arguments seems to stem from
SYNC, which choose the rule name sync_stat in the Fortran grammar. Therefore I
named the structure and participating routines the same. Th
On Thu, Apr 10, 2025 at 6:39 PM Jonathan Wakely wrote:
> On 10/04/25 11:24 +0200, Tomasz Kamiński wrote:
> >This patch implements part P2286R8 that specified debug (escaped)
> >format for the strings and characters sequences. This include both
> >handling of the '?' format specifier and set_debug
Am Donnerstag, dem 10.04.2025 um 17:05 + schrieb Qing Zhao:
> Hi, Martin,
>
> Thanks a lot for all your comments and questions, really helpful.
>
>
...
> >
> > An example I could imagine is when you memcpy
> > the struct. (but it is also not entirely clear why this
> > should not be allo
On Sun, Mar 9, 2025 at 1:35 PM Andrew Pinski wrote:
>
> LLVM folks noticed that GCC was shrink wrapping the call to
> vector::push_back.
> So I thought it was a good idea to commit a testcase to make sure GCC does
> not regress
> in this area unknowning.
>
> Note the shrink wrapping started with
On Wed, Apr 9, 2025 at 9:28 AM Luc Grosheintz
wrote:
> This implements std::extents from according to N4950 and
> contains partial progress towards PR107761.
>
> If an extent changes its type, there's a precondition in the standard,
> that the value is representable in the target integer type. T
> Am 10.04.2025 um 17:27 schrieb Jennifer Schmitz :
>
> This patch adds a test case to the testsuite for PR119706.
> The bug was already fixed by
> https://gcc.gnu.org/pipermail/gcc-patches/2025-April/680573.html.
>
> OK for mainline?
Ok
Richard
> Signed-off-by: Jennifer Schmitz
>
> gc
On 4/10/25 12:34 PM, Jason Merrill wrote:
On 4/8/25 10:29 AM, Patrick Palka wrote:
The template arguments aren't dependent however -- they're just
incomplete because when we deferred them we were in the middle
deduction, and we consider a NULL_TREE template argument as dependent.
I wonder what
On 10/04/2025 14:55, Christophe Lyon wrote:
> All arm effective-targets using check_runtime use the "_hw" or
> "_multilib" suffix, so rename arm_v8_1_lob_ok into arm_v8_1_lob_hw for
> consistency.
>
> gcc/testsuite/ChangeLog
>
> * lib/target-supports.exp: Rename arm_v8_1_lob_ok into
>
Hi, Martin,
Thanks a lot for all your comments and questions, really helpful.
> On Apr 10, 2025, at 01:41, Martin Uecker wrote:
>
> Am Mittwoch, dem 09.04.2025 um 18:31 + schrieb Qing Zhao:
>> Hi, Joseph and Martin,
>>
>> When I implemented the patch to attach the counted_by information to
It would be good to provide a macOS definition of is_debugger_present as
per https://developer.apple.com/library/archive/qa/qa1361/_index.html
but that isn't included in this change.
libstdc++-v3/ChangeLog:
* config.h.in: Regenerate.
* configure: Regenerate.
* configure.ac
On 4/9/25 11:11 AM, Patrick Palka wrote:
Bootstrap and regtest running on x86_64-pc-linux-gnu, does this look
OK for trunk/14 if successful?
OK.
On a similar note, as a small optimization in deduction_guides_for I
think we can replace the lookup_add loop with a single call to
lookup_add, but
I just pushed another eleven testcases, one of which is inspired by the
original PR.
> -Original Message-
> From: Richard Biener
> Sent: Thursday, April 10, 2025 01:14
> To: Robert Dubner
> Cc: Patches GCC
> Subject: Re: [committed] cobol: Proper comparison of alphanumeric to
> refmode
On 10/04/25 11:24 +0200, Tomasz Kamiński wrote:
This patch implements part P2286R8 that specified debug (escaped)
format for the strings and characters sequences. This include both
handling of the '?' format specifier and set_debug_format member.
To indicate partial support we define __glibcxx_f
On Wed, Apr 09, 2025 at 02:22:16PM +0200, Rainer Orth wrote:
> > Here is what I'm testing as an incremental fix, so far OK on x86_64-darwin
> > and powerpcle64 (GLIBC 2.34) .. others in progress. Does it help the
> > Solaris cases?
>
> I'll give it a try. Here's what I have (I believe it's more
On 4/8/25 10:29 AM, Patrick Palka wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look
OK for trunk?
OK.
-- >8 --
Here we substitute into the inner lambda twice, first during default
argument substitution for the outer template parameters, then during
that for the inner t
Am Donnerstag, dem 10.04.2025 um 10:55 -0400 schrieb Siddhesh Poyarekar:
> On 2025-04-10 10:50, Andrew MacLeod wrote:
> > Its not clear to me exactly what is being asked, but I think the
> > suggestion is that pointer references are being replaced with a builtin
> > function called .ACCESS_WITH_S
On 4/9/25 3:16 PM, Jakub Jelinek wrote:
Hi!
These pp_printf/pp_verbatim format strings should be gcc-internal-format,
they use the pretty-print.cc format specifier handling rather than libc
*printf, but pp_printf/pp_verbatim are intentionally not handled through
exgettext because not everything
The std::atomic constructor clears padding bits so that compare_exchange
will not fail due to differences in padding bits. But we can only do
that for C++14 and later, because in C++11 a constexpr constructor must
have an empty body. However, the code in compare_exchange_strong assumes
that padding
On 4/10/25 8:46 AM, Nathaniel Shead wrote:
Regression raised with my by private correspondance.
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
-- >8 --
My change in r15-9216 broke the case where we imported an uninstantiated
defaulted function over the top of one we had alread
For C++11 and later we can remvoe four overloads of _S_copy_chars and
use constexpr-if in the generic _S_copy_chars. This simplifies overload
resolution for _S_copy_chars, and also means that we optimize for other
iterators such as std::vector::iterator.
We still need all the _S_copy_chars overloa
The P3379R0 bump to __cpp_lib_constrained_equality relates to changes
that only affect std::expected, so there's no reason to define the
updated value in C++20.
This change restores the previous value (202403) for C++20, and only
uses the new value (202411) for C++23 and later.
Also remove the TO
Hi all,
attached patch reworks GET_TEAM(), TEAM_NUMBER() and IMAGE_STATUS() to adhere
to the Fortran 2018 as much as possible and to play nicely with the previous
patch of the TEAM statements.
Regtests ok on x86_64-pc-linux-gnu / F41. Ok for mainline?
Regards,
Andre
--
Andre Vehreschild
On 4/9/25 9:23 AM, Luc Grosheintz wrote:
This implements std::extents from according to N4950 and
contains partial progress towards PR107761.
If an extent changes its type, there's a precondition in the standard,
that the value is representable in the target integer type. This commit
uses a
On 2025-04-10 11:12, Martin Uecker wrote:
range-ops is setup to pull range information from builtin functions
already in gimple-range-op.cc::
gimple_range_op_handler::maybe_builtin_call (). We'd just need to write
a handler for this new one. You can pull information from 2 operands
under normal
This patch adds a test case to the testsuite for PR119706.
The bug was already fixed by
https://gcc.gnu.org/pipermail/gcc-patches/2025-April/680573.html.
OK for mainline?
Signed-off-by: Jennifer Schmitz
gcc/testsuite/
PR tree-optimization/119706
* g++.target/aarch64/sve/pr119706
On Thu, 10 Apr 2025 at 15:29, Hans-Peter Nilsson wrote:
>
> > From: Christophe Lyon
> > Date: Thu, 10 Apr 2025 15:21:23 +0200
>
> Not sure why I'm CC:ed on this one, not being a maintainer
> of the testsuite or targets where gcov tests are exercised,
Because you fixed a problem in r13-4103-ge91d
Hello,
I have another revision of this coming as I discovered some issues at
higher optimisation levels and have found a bunch of nits.
Kind regards,
Alfie
On 27/03/2025 15:45, Alfie Richards wrote:
Hi All,
This is an update on the patch series enabling ACLE compliant FMV
behaviour for targ
1 - 100 of 136 matches
Mail list logo
