Re: [PATCH v2 1/2] emit-rtl: Allow extra checks for paradoxical subregs [PR119966]

2025-06-07 Thread Stafford Horne
On Sat, Jun 07, 2025 at 06:53:28PM +0300, Dimitar Dimitrov wrote: > On Sat, Jun 07, 2025 at 11:38:46AM +0100, Stafford Horne wrote: > > On Fri, Jun 06, 2025 at 09:54:53PM +0100, Stafford Horne wrote: > > > On Fri, Jun 06, 2025 at 11:31:00PM +0300, Dimitar Dimitrov wrote: > > > > On Fri, Jun 06, 202

[to-be-committed][RISC-V] Add support for 32bit conditional move source/destinations on rv64

2025-06-07 Thread Jeff Law
Another hunk of work on riscv_expand_conditional_move from Shreya and myself. In this patch we're adding support for a sub-word src/destinations. This was originally more complex until the patches from Umesh reminded me that the czero patterns were written to support those cases. So we reall

[PATCH] math-opt: Remove special case of COND_EXPR

2025-06-07 Thread Andrew Pinski
Since r13-707-g68e0063397ba82 COND_EXPR in gimple assign does not have a special case for COND_EXPR and conditional as the first operand. This removes the code from tree-ssa-math-opts.cc which was for that special case. Bootstrapped and tested on x86_64-linux-gnu. PR tree-optimization/12

Re: [PATCH] Improve copy prop for aggregates and combine with zeroing case

2025-06-07 Thread Andrew Pinski
On Fri, Jun 6, 2025 at 11:50 AM Andrew Pinski wrote: > > This improves copy prop for aggregates by working over statements that don't > modify the access > just like how it is done for copying zeros. > To speed up things, we should only have one loop back on the vuse instead of > doing it twice

Re: [PATCH] expand: Improve store_field for `{}` stores of non mode size [PR110459]

2025-06-07 Thread Andrew Pinski
On Fri, Jun 6, 2025 at 12:02 PM Andrew Pinski wrote: > > On Thu, Jun 5, 2025 at 11:39 PM Richard Biener > wrote: > > > > On Fri, Jun 6, 2025 at 12:14 AM Andrew Pinski > > wrote: > > > > > > Currently we expand `{}` and store zeros to the stack and then do a full > > > mode load back. This is a

[PATCH 3/3] c: Add remove_qualifier helper function [PR120510]

2025-06-07 Thread Martin Uecker
Add a helper function to replace repeated code for removing qualifiers but not atomic. Make sure to also remove qualifiers but not atomic on the element type of arrays. PR c/120510 gcc/c/ChangeLog: * c-typeck.c (remove_qualifiers): New function. (composite_type_interna

[PATCH 2/3] c: partial fix for qualifier inconsistency II [PR120510]

2025-06-07 Thread Martin Uecker
This fixes a case where we invoke composite_type with types that do not have matching qualifiers. With this change, we can activate the checking assertion that makes sure the composite type is compatible with the two original types also for arrays. PR c/120510 gcc/c/ChangeLog:

[PATCH 1/3] c: partial fix for qualifier inconsistency [PR120510]

2025-06-07 Thread Martin Uecker
These three small patches fix some inconsistencies related to composite type which became apparent when moving the checking assertion. The first two are small fixes, while the third proposes to add a helper function for removing qualifers except atomic to make the code more robust. Bootstrappe

libstdc++: libstdc++: Implement LWG3528 make_from_tuple can perform (the equivalent of) a C-style cast

2025-06-07 Thread Yrong
Hi libstdc++ experts, This patch implement LWG3528 and also implement an improvement that makes std::make_from_tuple SFINAE friendly. I have implemented this LWG issue and SFINAE enhancements for libc++ and Microsoft STL. This is my first patch for libstdc++, hope I didn't missing anything. Pleas

Re: [PATCH v2 1/2] emit-rtl: Allow extra checks for paradoxical subregs [PR119966]

2025-06-07 Thread Dimitar Dimitrov
On Sat, Jun 07, 2025 at 11:38:46AM +0100, Stafford Horne wrote: > On Fri, Jun 06, 2025 at 09:54:53PM +0100, Stafford Horne wrote: > > On Fri, Jun 06, 2025 at 11:31:00PM +0300, Dimitar Dimitrov wrote: > > > On Fri, Jun 06, 2025 at 06:12:13PM +0100, Stafford Horne wrote: > > > > On Fri, Jun 06, 2025

[PATCH] gcc: middle-end opt for trigonometric pi-based functions builtins

2025-06-07 Thread Yuao Ma
Hi all, This patch has been updated to conditionally fold the specified math functions only when using MPFR version 4.2.0 or newer. To accompany this change, the test case now utilizes `__builtin_constant_p` to determine whether to execute the tests against the folded functions. Let me know if t

[PATCH v2] test: Do not include in g++.dg/modules/xtreme-header*.h

2025-06-07 Thread Jonathan Wakely
Including behaves differently depending on whether you have the TBB headers installed or not. Without them installed, the modules tests PASS, but with TBB headers installed they FAIL with: gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: internal compiler error: in core_vals, at cp/module.cc:66

Re: [PATCH v2 1/2] emit-rtl: Allow extra checks for paradoxical subregs [PR119966]

2025-06-07 Thread Stafford Horne
On Fri, Jun 06, 2025 at 09:54:53PM +0100, Stafford Horne wrote: > On Fri, Jun 06, 2025 at 11:31:00PM +0300, Dimitar Dimitrov wrote: > > On Fri, Jun 06, 2025 at 06:12:13PM +0100, Stafford Horne wrote: > > > On Fri, Jun 06, 2025 at 04:41:21PM +0100, Stafford Horne wrote: > > > > On Fri, Jun 06, 2025

[PATCH] gcc/configure: Check for makeinfo 5.0 or newer

2025-06-07 Thread Henrik Lindström
The build fails with older versions. Signed-off-by: Henrik Lindström --- gcc/configure| 2 +- gcc/configure.ac | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/configure b/gcc/configure index 776b0628c60..632fa6cb864 100755 --- a/gcc/configure +++ b/gcc/configure @@

[PATCH v2] expand: Improve expand_constructor for BLKmode mode and zeros constructors [PR110459]

2025-06-07 Thread Andrew Pinski
Currently expand_constructor when it comes to BLKmode types, we store out the constructor to memory. But for the zero case, we could just use `const_int 0` instead for types who are less than or equal to BITS_PER_WORD. This is only valid if we expanding without a target. This fixes the storing ze

Re: [PATCH] [lra] force reg update after spilling to memory [PR120424]

2025-06-07 Thread Denis Chertykov
Alexandre Oliva writes: > On Jun 6, 2025, Alexandre Oliva wrote: > >> Now, since lra_update_fp2sp_elimination checks that >> !elimination_fp2sp_occured_p, we *could* disable the fp2sp elimination, >> if it's selected, right away, so that it is not applied after we've >> disabled it, and then we