[PATCH v1 2/2] RISC-V: Add testcase for rv32 SAT_MUL from uint64

From: Pan Li Add the run and asm testcase for rv32 SAT_MUL, widen mul from uint8_t, uint16_t, uint32_t to uint64_t. gcc/testsuite/ChangeLog: * gcc.target/riscv/sat/sat_u_mul-1-u16-from-u64.c: New test. * gcc.target/riscv/sat/sat_u_mul-1-u32-from-u64.c: New test. * gcc.ta

[PATCH v1 1/2] Match: Leverage BITS_PER_WORD for unsigned SAT_MUL pattern

From: Pan Li The widen mul has different source type for differnt platform, like rv32 or rv64. For rv32, the source of widen mul is 32-bits while 64-bits in rv64. Thus, leverage HOST_WIDE_INT is not that correct and result in the pattern match failures in 32-bits system like rv32. Thus, levera

[PATCH v1 0/2] Refine the unsigned SAT_MUL for 32-bits like rv32

From: Pan Li The widen mul has different source type for differnt machines, like rv32 or rv64. The SAT_MUL pattern doesn't works well for backend like rv32 in previous, thus we would like to refine it by BITS_PER_WORD for precision check. The below test suites are passed for this patch: 1. The

Re: [PATCH, v2] Fortran: fix minor issues with coarrays (extended)

Hi Andre, Am 10.07.25 um 13:24 schrieb Andre Vehreschild: Hi Harald, sorry for all the confusion. Probably my understanding of a pure elemental routine is imperfect. I therefore first like to express what I need an a caf-accessor. In a caf-accessor I have only access to data that is "exported"

[PATCH v2] x86: Update MMXMODE:*mov_internal to support all 1s vectors

commit 77473a27bae04da99d6979d43e7bd0a8106f4557 Author: H.J. Lu Date: Thu Jun 26 06:08:51 2025 +0800 x86: Also handle all 1s float vector constant replaces (insn 29 28 30 5 (set (reg:V2SF 107) (mem/u/c:V2SF (symbol_ref/u:DI ("*.LC0") [flags 0x2]) [0 S8 A64])) 2031 {*movv2sf_inte

Re: [PATCH 2/2] Reduce the # of arguments of .ACCESS_WITH_SIZE from 6 to 4.

> On Jul 10, 2025, at 13:53, Jakub Jelinek wrote: > > On Thu, Jul 10, 2025 at 05:49:53PM +, Qing Zhao wrote: >> One more note here, previously, ACCESS_MODE has 5 values: >> -1: Unknown access semantics >> 0: none >> 1: read_only >> 2: write_only >> 3: read_write >>

Re: [PATCH 2/2] Reduce the # of arguments of .ACCESS_WITH_SIZE from 6 to 4.

On Thu, Jul 10, 2025 at 05:49:53PM +, Qing Zhao wrote: > One more note here, previously, ACCESS_MODE has 5 values: > -1: Unknown access semantics > 0: none > 1: read_only > 2: write_only > 3: read_write > > For counted_by, I passed “-1” to the .ACCESS_WITH_SIZE. >

Re: [PATCH] c++: P2036R3 - Change scope of lambda trailing-return-type [PR102610]

On 7/9/25 4:27 PM, Marek Polacek wrote: On Tue, Jul 08, 2025 at 12:15:03PM -0400, Jason Merrill wrote: 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 br

Re: [PATCH v2] arm.cc: fix thumb1 prologue high reg restore violates -ffixed-rX [PR117468]

Hi, Thanks for the update. There are still some formatting problems, some of which might be caused by your mailer. I manually applied the patch and manually triggered CI, the new test passed without regression. Here is the version I tested, let's wait for Richard's feedback. Christophe On Thu

Re: [PATCH] c++, v2: Implement C++26 P2786R13 - Trivial Relocatability [PR119064]

On 6/17/25 2:25 AM, Jakub Jelinek wrote: Hi! When writing the libstdc++ patch, I've noticed I've missed adding any testsuite coverage for __builtin_is_nothrow_relocatable trait. And got wrong the implementation as well, I thought type2 in that case should be the rvalue reference type to type1,

Re: [PATCH] c++: Save 8 further bytes from lang_type allocations

On 6/9/25 1:30 PM, Jakub Jelinek wrote: Hi! The following patch implements the /* FIXME reuse another field? */ comment on the lambda_expr member. I think (and asserts in the patch seem to confirm) CLASSTYPE_KEY_METHOD is only ever non-NULL for TYE_POLYMORPHIC_P and on the other side CLASSTYPE_

[To-commit][PATCH v2 1/2] Passing TYPE_SIZE_UNIT of the element as the 6th argument to .ACCESS_WITH_SIZE (PR121000)

This is the 2nd version based on Jacub's comments: a. Update the changelog; b. Update the testing case; bootstrapped and tested. I will commit this version soon. thanks. Qing. === The size of the element of the FAM _cannot_ reliably depends on the original

[RFC] c++: Quoting in -fmodules-mapper [PR110153]

Users might be using a space in their build directory path. To allow specifying such a root for the module mapper started by GCC, we need the command to allow quotes. Previously quoting a path passed to the module mapper was not possible, so replace the custom argv parsing with wordexp(), which sup

[PATCH 1/3] fortran: Generate array reallocation out of loops

From: Mikael Morin Regression tested on x86_64-pc-linux-gnu. OK for master? -- >8 -- Generate the array reallocation on assignment code before entering the scalarization loops. This doesn't move the generated code itself, which was already put before the outermost loop, but only changes the cu

[pushed] testsuite: Fix unallocated array usage in test

Le 08/07/2025 à 22:17, Harald Anlauf a écrit : A corresponding fix is approved. For some reason the sanitizers didn't work on my machine, they didn't work on cfarm135, but I was able to confirm they were catching an error on the testcase on cfarm421. Now fixed.From ca034694757f0fb3461a1d0c

Re: [PATCH] c, c++: Extend -Wunused-but-set-* warnings [PR44677]

On 4/24/25 3:50 AM, Jakub Jelinek wrote: Hi! The -Wunused-but-set-* warnings work by using 2 bits on VAR_DECLs & PARM_DECLs, TREE_USED and DECL_READ_P. If neither is set, we typically emit -Wunused-variable or -Wunused-parameter warning, that is for variables which are just declared (including

[RFC v2] c++: Quoting in -fmodules-mapper [PR110153]

Users might be using a space in their build directory path. To allow specifying such a root for the module mapper started by GCC, we need the command to allow quotes. Previously quoting a path passed to the module mapper was not possible, so replace the custom argv parsing with the argv parsing log

Re: [PATCH 1/2] libstdc++: Treat __int128 as a real integral type [PR96710]

On Wed, 9 Jul 2025, Jonathan Wakely wrote: > Since LWG 3828 (included in C++23) implementations are allowed to have > extended integer types that are wider than intmax_t. This means we no > longer have to make is_integral_v<__int128> false for strict -std=c++23 > mode, removing the confusing incon

Re: [PATCH 2/2] libstdc++: Always treat __float128 as a floating-point type

On Wed, 9 Jul 2025, Jonathan Wakely wrote: > Similar to the previous commit that made is_integral_v<__int128> > unconditionally true, this makes is_floating_point_v<__float128> > unconditionally true. With the new extended floating-point types in > C++23 (std::float64_t etc.) it seems unhelpful fo

Re: [RFC] c++: Quoting in -fmodules-mapper [PR110153]

On Thu, Jul 10, 2025 at 12:05 PM Nicolas Werner wrote: > > Users might be using a space in their build directory path. To allow > specifying such a root for the module mapper started by GCC, we need the > command to allow quotes. Previously quoting a path passed to the module > mapper was not poss

RE: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.

Excerpts from Robert Dubner's message of Juli 9, 2025 4:32 pm: > With respect, this is another example of "I have been unable to make it > work." > > The gcc/Makefile.in has this line in it: > > $(foreach file,$(ALL_HOST_FRONTEND_OBJS),$(eval CFLAGS-$(file) += > -DIN_GCC_FRONTEND)) > > At the po

[PATCH] [arm] prevent impossible tail- long-calls with static chain [PR119430]

When a function call uses up all argument registers, and needs IP for the static chain, there isn't any call-clobbered register left for reload to assign as the sibcall target, when -mlong-calls is enabled. Use the same logic that does the job for indirect calls to prevent tail calls in this case

Re: [PATCH] x86: Update "*mov_internal" in mmx.md to handle all 1s vectors

On Thu, Jul 10, 2025 at 9:44 PM Uros Bizjak wrote: > > On Thu, Jul 10, 2025 at 2:31 PM Uros Bizjak wrote: > > > > On Thu, Jul 10, 2025 at 1:57 PM H.J. Lu wrote: > > > > > > commit 77473a27bae04da99d6979d43e7bd0a8106f4557 > > > Author: H.J. Lu > > > Date: Thu Jun 26 06:08:51 2025 +0800 > > > >

Re: [PATCH] libstdc++: Fix __uninitialized_default for constexpr case

On Tue, 8 Jul 2025, Jonathan Wakely wrote: > We should not use the std::fill optimization for trivial types during > constant evaluation, because we need to begin the lifetime of all > objects, even trivially default constructible ones. > > This fixes a bug that Clang diagnosed: > > include/c++/

Re: [PATCH 1/2] [APX CFCMOV] Support APX CFCMOV in if_convert pass

Ping, hopefully someone can help review this part Hongyu Wang 于2025年5月21日周三 09:09写道： > > From: Lingling Kong > > Hi, > > APX CFCMOV feature implements conditionally faulting which means > that all memory faults are suppressed when the condition code > evaluates to false and load or store a memor

RE: [PATCH] Reject single lane vector types for SLP build

> -Original Message- > From: Richard Biener > Sent: Thursday, July 10, 2025 6:42 PM > To: Tamar Christina > Cc: gcc-patches@gcc.gnu.org; Richard Sandiford ; > CI RISC-V > Subject: Re: [PATCH] Reject single lane vector types for SLP build > > > > > Am 10.07.2025 um 16:27 schrieb Tamar

[PATCH 3/3] fortran: Amend descriptor bounds init if unallocated

From: Mikael Morin Regression tested on x86_64-pc-linux-gnu. OK for master? -- >8 -- Always generate the conditional initialization of unallocated variables regardless of the basic variable allocation tracking done in the frontend and with an additional always false condition. The scalarizer u

[PATCH 0/3] fortran: Reallocation on assignment tweaks

From: Mikael Morin Hello, here are three patches as follow-up to this message. These started as an attempt to remove the PR fortran/108889 workaround, which I didn't understand. I had to keep it in the end but this is what I could save from that failed attempt. Regression tested on x86_64-pc-li

[PATCH 2/3] fortran: Delay evaluation of array bounds after reallocation

From: Mikael Morin Regression tested on x86_64-pc-linux-gnu. OK for master? -- >8 -- Delay the evaluation of bounds, offset, etc after the reallocation, for the scalarization of allocatable arrays on the left hand side of assignments. Before this change, the code preceding the scalarization lo

คุณเดือดร้อน เราช่วยคุณได้ ไม่มีโอนก่อนไม่มีมัดจำ

Re: [PATCH] c++, v2: Don't incorrectly reject override after class head name [PR120569]

On 6/9/25 1:19 PM, Jakub Jelinek wrote: On Mon, Jun 09, 2025 at 12:17:12PM -0400, Jason Merrill wrote: While the https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p2786r13.html#c03-compatibility-changes-for-annex-c-diff.cpp03.dcl.dcl hunk dropped because struct C {}; struct C {} final {};

[pushed] aarch64: Guard VF-based costing with !m_costing_for_scalar

g:4b47acfe2b626d1276e229a0cf165e934813df6c caused a segfault in aarch64_vector_costs::analyze_loop_vinfo when costing scalar code, since we'd end up dividing by a zero VF. Much of the structure of the aarch64 costing code dates from a stage 4 patch, when we had to work within the bounds of what th

Re: [PATCH] c++: Fix up final handling in C++98 [PR120628]

On 6/12/25 3:11 AM, Jakub Jelinek wrote: Hi! The following patch is on top of the https://gcc.gnu.org/pipermail/gcc-patches/2025-June/686210.html patch which stopped treating override as conditional keyword in class properties. This PR mentions another problem; we emit a bogus warning on code li

[PATCH] c++, v3: Implement C++26 P2786R13 - Trivial Relocatability [PR119064]

On Thu, Jul 10, 2025 at 05:46:06PM -0400, Jason Merrill wrote: > > + bool trivially_relocatable_if_eligible : 1; > > + bool replaceable_if_eligible : 1; > > + > > + bool trivially_relocatable : 1; > > + bool trivially_relocatable_computed : 1; > > + bool replaceable : 1; > > + bool replaceabl

[PATCH] RISC-V: Add testcases for unsigned vector SAT_SUB form 11 and form 12

From: panciyan This patch adds testcase for form11 and form12, as shown below: void __attribute__((noinline)) \ vec_sat_u_sub_##T##_fmt_11 (T *out, T *op_1, T *op_2, unsigned limit) \ {\ u

[PATCH] testsuite: Disable musttail tests if target uses SJLJ exceptions

A few tests started failing recently on pru-unknown-elf because it uses SJLJ implementation for exceptions: FAIL: g++.dg/ext/musttail3.C -std=c++11 (test for excess errors) .../gcc/gcc/testsuite/g++.dg/ext/musttail3.C:12:34: error: cannot tail-call: caller uses sjlj exceptions Fix by disabli

Re: [PATCH v3] arm.cc: fix thumb1 size-optimized function prolog violates -ffixed-rX [PR117366]

Thanks for the update. Like in your other email, there are still formatting issues. Here is the version I applied manually and used in CI. Christophe On Thu, 10 Jul 2025 at 01:46, Matt Parks wrote: > > This patch fixes PR117366: > arm thumb1 epilogue size optimizer violates -ffixed-r4. > > gcc

[PATCH] ipa: Disallow signature changes in fun->has_musttail functions [PR121023]

Hi! As the following testcase shows e.g. on ia32, letting IPA opts change signature of functions which have [[{gnu,clang}::musttail]] calls can turn programs that would be compiled normally into something that is rejected because the caller has fewer argument stack slots than the function being ta

Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.

On Tue, 8 Jul 2025 16:59:36 -0500 (CDT) Robert Dubner wrote: > > Does that not suffice? > > I don't think it does. > > I am forced, for roughly the fourth time, to establish my > requirements: > > 1) I want, for development, to be able to establish flags for the > COBOL front end -- independen

RE: [PATCH] RISC-V: Add testcases for unsigned vector SAT_SUB form 11 and form 12

Ok, thanks. Pan -Original Message- From: Ciyan Pan Sent: Friday, July 11, 2025 10:35 AM To: gcc-patches@gcc.gnu.org Cc: kito.ch...@gmail.com; richard.guent...@gmail.com; tamar.christ...@arm.com; juzhe.zh...@rivai.ai; Li, Pan2 ; jeffreya...@gmail.com; rdapp@gmail.com; panciyan Sub

<    1   2