[PING][PATCH v3] Add new warning Wmissing-designated-initializers [PR39589]

Ping https://gcc.gnu.org/pipermail/gcc-patches/2025-January/672568.html Missed the version 15 freeze with the last ping, I believe the project is open for general development again now?

Re: PING: [PATCH] x86: Add a pass to remove redundant all 0s/1s vector load

On Mon, Apr 21, 2025 at 4:30 PM H.J. Lu wrote: > > On Mon, Apr 21, 2025 at 11:29 AM Hongtao Liu wrote: > > > > On Sat, Apr 19, 2025 at 1:25 PM H.J. Lu wrote: > > > > > > On Sun, Dec 1, 2024 at 7:50 AM H.J. Lu wrote: > > > > > > > > For all different modes of all 0s/1s vectors, we can use the si

Re: PING: [PATCH] x86: Add a pass to remove redundant all 0s/1s vector load

On Mon, Apr 21, 2025 at 11:29 AM Hongtao Liu wrote: > > On Sat, Apr 19, 2025 at 1:25 PM H.J. Lu wrote: > > > > On Sun, Dec 1, 2024 at 7:50 AM H.J. Lu wrote: > > > > > > For all different modes of all 0s/1s vectors, we can use the single widest > > > all 0s/1s vector register for all 0s/1s vector

Re: PING: [PATCH] x86: Add a pass to remove redundant all 0s/1s vector load

On Sat, Apr 19, 2025 at 1:25 PM H.J. Lu wrote: > > On Sun, Dec 1, 2024 at 7:50 AM H.J. Lu wrote: > > > > For all different modes of all 0s/1s vectors, we can use the single widest > > all 0s/1s vector register for all 0s/1s vector uses in the whole function. > > Add a pass to generate a single wi

Ping [PATCH/RFC] target, hooks: Allow a target to trap on unreachable [PR109267].

Hi all, I’d like to ping the patch from April 2024 at https://gcc.gnu.org/pipermail/gcc-patches/2024-May/651100.html As far as I understand, the status of this is: - Iain posted the patch for review - Richard said "your target hook is reasonable though I'd name it expand_unreachable_as_trap may

Re: PING: [PATCH v2] x86: Add pcmpeq splitters

On Sat, Apr 19, 2025 at 4:16 PM Uros Bizjak wrote: > > On Sat, Apr 19, 2025 at 7:22 AM H.J. Lu wrote: > > > > On Mon, Dec 2, 2024 at 6:27 AM H.J. Lu wrote: > > > > > > Add pcmpeq splitters to split > > > > > > (insn 5 3 7 2 (set (reg:V4SI 100) > > > (eq:V4SI (reg:V4SI 98) > > >

Re: PING: [PATCH v2] x86: Add pcmpeq splitters

On Sat, Apr 19, 2025 at 7:22 AM H.J. Lu wrote: > > On Mon, Dec 2, 2024 at 6:27 AM H.J. Lu wrote: > > > > Add pcmpeq splitters to split > > > > (insn 5 3 7 2 (set (reg:V4SI 100) > > (eq:V4SI (reg:V4SI 98) > > (reg:V4SI 98))) 7910 {*sse2_eqv4si3} > > (expr_list:REG_DEAD (re

PING: [PATCH] x86: Add a pass to remove redundant all 0s/1s vector load

On Sun, Dec 1, 2024 at 7:50 AM H.J. Lu wrote: > > For all different modes of all 0s/1s vectors, we can use the single widest > all 0s/1s vector register for all 0s/1s vector uses in the whole function. > Add a pass to generate a single widest all 0s/1s vector set instruction at > entry of the near

PING: [PATCH v2] x86: Add pcmpeq splitters

On Mon, Dec 2, 2024 at 6:27 AM H.J. Lu wrote: > > Add pcmpeq splitters to split > > (insn 5 3 7 2 (set (reg:V4SI 100) > (eq:V4SI (reg:V4SI 98) > (reg:V4SI 98))) 7910 {*sse2_eqv4si3} > (expr_list:REG_DEAD (reg:V4SI 98) > (expr_list:REG_EQUAL (eq:V4SI (const_vector:V

Re: [PING][PATCH] doc: Clarify REG_EH_REGION note usage

Applied to trunk, thank you! --Philipp. On Thu, 17 Apr 2025 at 21:51, Jeff Law wrote: > > > > On 4/8/25 6:12 AM, Konstantinos Eleftheriou wrote: > > Hi, > > Just a ping for https://gcc.gnu.org/pipermail/gcc-patches/2025- > > March/677635.html >

Re: [PING][PATCH] doc: Clarify REG_EH_REGION note usage

On 4/8/25 6:12 AM, Konstantinos Eleftheriou wrote: Hi, Just a ping for https://gcc.gnu.org/pipermail/gcc-patches/2025- March/677635.html . OK for the trunk. I don't think it's worth porting to the release branches. jeff

[PING][PATCH][gcc-14] libcpp: Fix incorrect line numbers in large files [PR108900]

From: Jeremy Bettis This patch addresses an issue in the C preprocessor where incorrect line number information is generated when processing files with a large number of lines. The problem arises from improper handling of location intervals in the line map, particularly when locations exceed LINE

[PING][PATCH] doc: Clarify REG_EH_REGION note usage

Hi, Just a ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-March/677635.html. Thanks, Konstantinos

[PING][PATCH v3] reassoc: Optimize CMP/XOR expressions [PR116860]

Hi, Just a ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-March/677788.html . Thanks, Konstantinos

RE: [ping][PATCH] libgcobol: Provide fallbacks for C32 strfromf32/64 [PR119296].

gt; From: Iain Sandoe > Sent: Wednesday, April 2, 2025 14:24 > To: GCC Patches > Cc: James K. Lowden ; Robert Dubner > > Subject: [ping][PATCH] libgcobol: Provide fallbacks for C32 strfromf32/64 > [PR119296]. > > Hi folks, > it would be great to reduce the in-flight patc

RE: [ping][PATCH] libgcobol: Provide fallbacks for C32 strfromf32/64 [PR119296].

> -Original Message- > From: Iain Sandoe > Sent: Wednesday, April 2, 2025 15:05 > To: Robert Dubner > Cc: GCC Patches ; James K. Lowden > > Subject: Re: [ping][PATCH] libgcobol: Provide fallbacks for C32 > strfromf32/64 [PR119296]. > > > > > On 2 A

Re: [ping][PATCH] libgcobol: Provide fallbacks for C32 strfromf32/64 [PR119296].

red out how to handle our > joint responsibility. understood.. > > Hence delays. … will try not to hassle too much :) > > >> -Original Message- >> From: Iain Sandoe >> Sent: Wednesday, April 2, 2025 14:24 >> To: GCC Patches >> Cc: James K. Lowden ; Ro

[ping][PATCH] libgcobol: Provide fallbacks for C32 strfromf32/64 [PR119296].

Hi folks, it would be great to reduce the in-flight patch stack a bit :) > On 25 Mar 2025, at 16:40, Iain Sandoe wrote: > > This is on top of the C++-ify configure and random_r patches. > Tested on x86_64,aarch64-Linux and x86_64-darwin, OK for trunk? > thanks > Iain > > --- 8< --- > > strfro

Re: Patch ping [PATCH] tailc: Don't fail musttail calls if they use or could use local arguments, instead warn [PR119376]

On Tue, 1 Apr 2025, Jakub Jelinek wrote: > Hi! > > On Tue, Mar 25, 2025 at 08:34:10AM +0100, Jakub Jelinek wrote: > > As discussed here and in bugzilla, [[clang::musttail]] attribute in clang > > not just strongly asks for tail call or error, but changes behavior. > > To quote: > > https://clang.

Patch ping [PATCH] tailc: Don't fail musttail calls if they use or could use local arguments, instead warn [PR119376]

Hi! On Tue, Mar 25, 2025 at 08:34:10AM +0100, Jakub Jelinek wrote: > As discussed here and in bugzilla, [[clang::musttail]] attribute in clang > not just strongly asks for tail call or error, but changes behavior. > To quote: > https://clang.llvm.org/docs/AttributeReference.html#musttail > "The li

Re: Patch ping [PATCH] tailc: Don't fail musttail calls if they use or could use local arguments, instead warn [PR119376]

> I'd like to ping the > https://gcc.gnu.org/pipermail/gcc-patches/2025-March/679182.html > patch. > I know it is quite controversial and if clang wouldn't be the first > to implement this I'd certainly not go that way; I am willing to change > the warning option names or move the maybe one from -W

[ping] [PATCH] libgcobol: C++-ify the configuration steps.

Hi folks > On 24 Mar 2025, at 17:15, Iain Sandoe wrote: > >> On 24 Mar 2025, at 16:41, Iain Sandoe wrote: >>> On 24 Mar 2025, at 16:38, Robert Dubner wrote: >>> >>> How about you create the new patch and just edit out the regenerated >>> configure before sending the e-mail? Typing "autorecon

[ping][PATCH v2] aarch64, Darwin: Initial implementation of Apple cores [PR113257].

I realise this is probably not #1 priority - but it would be nice to have in gcc-15. thanks iain > On 22 Mar 2025, at 14:31, Iain Sandoe wrote: > > 0. Sorry this has taken some time to close off; partly because of waiting > for input, but mostly that I've been stretched with other work. > 1.

Re: [PING][PATCH v3 0/4] Fix data races with sub-longword accesses on Alpha

On Sat, 22 Mar 2025, Maciej W. Rozycki wrote: > > This is v3 of the series comprising the final 4 outstanding changes. I > > note that the corresponding v2 patches have been approved, but concerns > > were discussed, which this update has addressed. > > Ping for: >

[ping] [PATCH] includes, Darwin: Handle modular use for macOS SDKs [PR116827].

C++ modules are not really usable on latest Darwin without resolving this, thanks Iain > On 23 Mar 2025, at 12:29, Iain Sandoe wrote: > > From: Iain Sandoe > > Tested on x86_64/aarch64 Darwin and x86_64-linux, > OK for trunk? > backports to branches supporting modules? > thanks > Iain > > ---

[ping] [PATCH] libiberty, gcc: Add memrchr to libiberty and use it [PR119283].

this (or an alternate implementation) is needed for the cobol FE to build on darwin, > On 21 Mar 2025, at 10:00, Iain Sandoe wrote: > > It seems that libiberty already has replacements for most of the > mem* functions, but they are not published via include/libiberty.h. > > Tested on x86_64 Li

ping: [PATCH] c-family: Improve location for -Wunknown-pragmas in a _Pragma [PR118838]

Hello- May I please ping this patch? Thanks! https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675645.html -Lewis On Wed, Feb 12, 2025 at 8:27 PM Lewis Hyatt wrote: > > Hello- > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118838 > > This patch addresses the issue mentioned in the PR (a

[PING][PATCH] Makefile.tpl: Implement per-stage GDCFLAGS [PR116975]

Ping. Excerpts from Iain Buclaw's message of März 3, 2025 11:14 pm: > Hi, > > This patch implements STAGE1_GDCFLAGS and others to the configure > machinery, allowing the GDCFLAGS for each bootstrap stage of building > gdc to be overriden, as is the case with CXXFLAGS for other front-ends. > > Th

[PING][PATCH v3 0/4] Fix data races with sub-longword accesses on Alpha

On Tue, 11 Mar 2025, Maciej W. Rozycki wrote: > This is v3 of the series comprising the final 4 outstanding changes. I > note that the corresponding v2 patches have been approved, but concerns > were discussed, which this update has addressed. Ping for:

Ping [PATCH 0/2] v2 Add prime path coverage to gcc/gcov

Ping. On 3/5/25 20:21, Jørgen Kvalsvik wrote: Ping. On 2/21/25 19:15, Jørgen Kvalsvik wrote: Ping On 2/12/25 16:30, Jørgen Kvalsvik wrote: I have applied fixes for everything in the last review, plus some GNU style fixes that I had missed previously. We have tested and used a build with this

Ping: [PATCH v4] get source line for diagnostic from preprocessed file [PR preprocessor/79106]

Gentle ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-March/676875.html

[PING] [PATCH v3] c++: Use capture from outer lambda, if any, instead of erroring out [PR110584]

Hi, On Thu Mar 6, 2025 at 8:06 PM CET, Simon Martin wrote: > Hi Jason, > > On Wed Mar 5, 2025 at 9:40 PM CET, Jason Merrill wrote: >> On 3/5/25 10:39 AM, Simon Martin wrote: >>> Hi Jason, >>> >>> On Wed Mar 5, 2025 at 12:03 AM CET, Jason Merrill wrote: On 2/18/25 5:12 AM, Simon Martin wrote:

Re: [Ping, Patch, www-docs, Fortran, Coarray-ABI] Announce coarray-ABI changes in gfortran-15

PING! On Thu, 20 Feb 2025 10:54:30 +0100 Andre Vehreschild wrote: > Hi all, > > attached patch makes an attempt to announce the ABI-changes in the coarrays > library. Me being German always has difficulties to find a proper wording. So > please propose improvements. > > Stupid question: How to I

Re: [Ping, Patch, www-docs, Fortran, Coarray-ABI] Announce coarray-ABI changes in gfortran-15

On 3/10/25 9:57 AM, Jerry D wrote: On 3/10/25 1:08 AM, Andre Vehreschild wrote: Hi Steve and Jerry, thanks for the review and the proposed changes. I have based on them, but needed to adapt some places, because the meaning was changed. Can you please take another look? Jerry, where do I find

Re: [Ping, Patch, www-docs, Fortran, Coarray-ABI] Announce coarray-ABI changes in gfortran-15

On 3/10/25 1:08 AM, Andre Vehreschild wrote: Hi Steve and Jerry, thanks for the review and the proposed changes. I have based on them, but needed to adapt some places, because the meaning was changed. Can you please take another look? Jerry, where do I find this check-script? In bin/ nothing ju

[PING][PATCH] Alpha: Fix base block alignment calculation regression

On Tue, 25 Feb 2025, Maciej W. Rozycki wrote: > Address this issue by recursing into COMPONENT_REF tree nodes until the > outermost one has been reached, which is supposed to be a MEM_REF one, > accumulating the offset as we go, fixing a commit e0dae4da4c45 ("Alpha: > Also use tree information

Re: [Ping, Patch, www-docs, Fortran, Coarray-ABI] Announce coarray-ABI changes in gfortran-15

Hi Jerry, thanks for the review. Committed as 87c7db8b1b2c1484d6de3331098669735d33f95e. I also had it checked using the W3C validator w/o any errors. Therefore committed. Thanks again, Andre On Mon, 10 Mar 2025 10:01:46 -0700 Jerry D wrote: > On 3/10/25 9:57 AM, Jerry D wrote: > > On

Re: Ping: [PATCH] LoongArch: combine related slli operations

在 2025/3/10 下午3:24, Zhou Zhao 写道: Ping Hi, You need to send another patch for version V2 with modifications. However, I am currently testing the value of align, and GCC15 is already in stage 4, so this patch might have to wait until the GCC16 stage 1 phase before it can be integrated.

Re: [Ping, Patch, www-docs, Fortran, Coarray-ABI] Announce coarray-ABI changes in gfortran-15

Hi Steve and Jerry, thanks for the review and the proposed changes. I have based on them, but needed to adapt some places, because the meaning was changed. Can you please take another look? Jerry, where do I find this check-script? In bin/ nothing jumps out at me to be a check-script. Thanks,

Ping: [PATCH] LoongArch: combine related slli operations

Ping 在 2025/1/7 下午8:45, Zhou Zhao 写道: 在 2025/1/7 下午7:49, Lulu Cheng 写道: 在 2025/1/2 下午5:46, Zhou Zhao 写道: If SImode reg is continuous left shifted twice, combine related instruction to one. gcc/ChangeLog: * config/loongarch/loongarch.md (extsv_ashlsi3):     New template Hi, zhaozhou:

Ping: [PATCH v2 1/5][STAGE1] c-family: add btf_type_tag and btf_decl_tag attributes

Ping. this patch: https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675242.html series: https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675241.html On 2/6/25 11:54, David Faust wrote: > Add two new c-family attributes, "btf_type_tag" and "btf_decl_tag" > along with a simple shar

Ping: [PATCH v2 2/5][STAGE1] dwarf: create annotation DIEs for btf tags

Ping. Patches 3-5 in the series have been reviewed, but depend heavily upon the DWARF implementation in this patch. It would be useful to have some indication of whether the new DWARF implementation is generally OK... Richard, your feedback on earlier iterations was very helpful, maybe you could

Re: [Ping, Patch, www-docs, Fortran, Coarray-ABI] Announce coarray-ABI changes in gfortran-15

On 3/6/25 10:02 AM, Steve Kargl wrote: Andre, Here's a bit of wordsmith. I removed the abbreviation "Esp." I'm not sure if there is additional markup needed; especially, with the "-fcoarray=single" I inserted. Coarray support has been reworked to allow access to components in derived typ

Re: [Ping, Patch, www-docs, Fortran, Coarray-ABI] Announce coarray-ABI changes in gfortran-15

Andre, Here's a bit of wordsmith. I removed the abbreviation "Esp." I'm not sure if there is additional markup needed; especially, with the "-fcoarray=single" I inserted. Coarray support has been reworked to allow access to components in derived types that have not been compiled with coarray

Ping [PATCH] Record, report basic blocks of conditional exprs

Ping. On 2/12/25 19:00, Jørgen Kvalsvik wrote: Ping. On 1/31/25 10:35, Jørgen Kvalsvik wrote: Record basic blocks that make up a conditional expression with -fcondition-coverage and report when using the gcov -w/--verbose flag. This makes the report more accurate when basic blocks are included

Ping [PATCH 0/2] v2 Add prime path coverage to gcc/gcov

Ping. On 2/21/25 19:15, Jørgen Kvalsvik wrote: Ping On 2/12/25 16:30, Jørgen Kvalsvik wrote: I have applied fixes for everything in the last review, plus some GNU style fixes that I had missed previously. We have tested and used a build with this applied for 3-4 months now and haven't run into

[PING] [PATCH] c++: Don't replace INDIRECT_REFs by a const capture proxy too eagerly [PR117504]

Hi, On 14 Feb 2025, at 18:08, Simon Martin wrote: > We have been miscompiling the following valid code since GCC8, and > r8-3497-g281e6c1d8f1b4c > > === cut here === > struct span { > span (const int (&__first)[1]) : _M_ptr (__first) {} > int operator[] (long __i) { return _M_ptr[__i]; } >

[PING] [PATCH] c++: Use capture from outer lambda, if any, instead of erroring out [PR110584]

Hi, On 18 Feb 2025, at 11:12, Simon Martin wrote: > We've been rejecting this valid code since r8-4571: > > === cut here === > void foo (float); > int main () { > constexpr float x = 0; > (void) [&] () { > foo (x); > (void) [] () { > foo (x); > }; > }; > } > === cut here =

[PING] [PATCH] c++: Fix checking assert upon invalid class definition [PR116740]

Hi, On 18 Feb 2025, at 14:00, Simon Martin wrote: > A checking assert triggers upon the following invalid code since > GCC 11: > > === cut here === > class { a (struct b; > } struct b > === cut here === > > The problem is that during error recovery, we call > set_identifier_type_value_with_scope

[PING] [PATCH v3] get source line for diagnostic from preprocessed file [PR preprocessor/79106]

Gentle ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675450.html

Ping [PATCH 0/2] v2 Add prime path coverage to gcc/gcov

Ping On 2/12/25 16:30, Jørgen Kvalsvik wrote: I have applied fixes for everything in the last review, plus some GNU style fixes that I had missed previously. We have tested and used a build with this applied for 3-4 months now and haven't run into any issues. Jørgen Kvalsvik (2): gcov: branc

Ping: [PATCH v2 0/5][STAGE1] Add btf_decl_tag and btf_type_tag C attributes

Gentle ping for this series. https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675241.html On 2/6/25 11:54, David Faust wrote: > [v1: https://gcc.gnu.org/pipermail/gcc-patches/2024-October/666911.html > Changes from v1: > - Fix a bug in v1 related to generating DWARF for type tags applie

Re: Ping: [PATCH] testsuite: Fix up toplevel-asm-1.c for LoongArch

在 2025/2/19 下午3:27, Xi Ruoyao 写道: On Wed, 2025-02-05 at 08:57 +0800, Xi Ruoyao wrote: Like RISC-V, on LoongArch we don't really support %cN for SYMBOL_REFs even with -fno-pic. gcc/testsuite/ChangeLog: * c-c++-common/toplevel-asm-1.c: Use %cc3 %cc4 instead of %c3 %c4 on LoongA

Ping: [PATCH] testsuite: Fix up toplevel-asm-1.c for LoongArch

On Wed, 2025-02-05 at 08:57 +0800, Xi Ruoyao wrote: > Like RISC-V, on LoongArch we don't really support %cN for SYMBOL_REFs > even with -fno-pic. > > gcc/testsuite/ChangeLog: > > * c-c++-common/toplevel-asm-1.c: Use %cc3 %cc4 instead of %c3 > %c4 on LoongArch. > --- > > Ok for trunk?

Re: Ping: [PATCH] late-combine: Tighten register class check [PR108840]

On 2/17/25 4:33 AM, Richard Sandiford wrote: Ping Feel through the cracks. We really should acknowledge that you know this code better than anyone and shouldn't need to wait on review. Anyway, LGTM. jeff

Re: [PING][PATCH v2] libcpp: Fix incorrect line numbers in large files [PR108900]

Hi, you may want to Cc Lewis Hyatt on such patches (adding him now), I didn't touch this area. Alexander On Mon, 17 Feb 2025, yash.shi...@windriver.com wrote: > From: Yash Shinde > > This patch addresses an issue in the C preprocessor where incorrect line > number information is generated wh

Ping: [PATCH] late-combine: Tighten register class check [PR108840]

Ping Richard Sandiford writes: > gcc.target/aarch64/pr108840.c has failed since r15-268-g9dbff9c05520 > (which means that I really ought to have looked at it earlier). > > The test wants us to fold an SImode AND into all shifts that use it. > This is something that late-combine is supposed to do,

[PING][PATCH v2] libcpp: Fix incorrect line numbers in large files [PR108900]

From: Yash Shinde This patch addresses an issue in the C preprocessor where incorrect line number information is generated when processing files with a large number of lines. The problem arises from improper handling of location intervals in the line map, particularly when locations exceed LINE

[PING][PATCH v2] libcpp: Fix incorrect line numbers in large files [PR108900]

From: Yash Shinde This patch addresses an issue in the C preprocessor where incorrect line number information is generated when processing files with a large number of lines. The problem arises from improper handling of location intervals in the line map, particularly when locations exceed LINE

Ping [PATCH] Record, report basic blocks of conditional exprs

Ping. On 1/31/25 10:35, Jørgen Kvalsvik wrote: Record basic blocks that make up a conditional expression with -fcondition-coverage and report when using the gcov -w/--verbose flag. This makes the report more accurate when basic blocks are included as there may be blocks in-between the actual Boo

Re: [PING][PATCH v3] Add new warning Wmissing-designated-initializers [PR39589]

On 2/5/25 3:43 PM, Peter Frost wrote: Ping https://gcc.gnu.org/pipermail/gcc-patches/2025-January/672568.html We're in regression fixes only phase of our development cycle. This doesn't fix a regression, so it'll need to wait for the next development window to open before it gets further at

[PING][PATCH v3] Add new warning Wmissing-designated-initializers [PR39589]

Ping https://gcc.gnu.org/pipermail/gcc-patches/2025-January/672568.html

Re: [PING, PATCH] fortran: fix -MT/-MQ adding additional target [PR47485]

Committed as: commit e41a5a2a0832509fa1c0b7cab0c8001fadbd23d4 (HEAD -> master, origin/master, origin/HEAD) Author: Jerry DeLisle Date: Tue Feb 4 17:21:42 2025 -0800 Fortran: Fix PR 47485. The -MT and -MQ options should replace the default target in the generated dependency file

Re: [PING, PATCH] fortran: fix -MT/-MQ adding additional target [PR47485]

On 2/4/25 9:29 AM, Jerry D wrote: On 2/3/25 4:46 PM, Vincent Vanlaer wrote: On 4/02/2025 01:42, Jerry D wrote: On 2/3/25 2:14 PM, Vincent Vanlaer wrote: Hi all, Gentle ping for the patch below: https://gcc.gnu.org/pipermail/ fortran/2024-December/061467.html Best wishes, Vincent On 30/

Re: [PING, PATCH] fortran: fix -MT/-MQ adding additional target [PR47485]

On 2/3/25 4:46 PM, Vincent Vanlaer wrote: On 4/02/2025 01:42, Jerry D wrote: On 2/3/25 2:14 PM, Vincent Vanlaer wrote: Hi all, Gentle ping for the patch below: https://gcc.gnu.org/pipermail/ fortran/2024-December/061467.html Best wishes, Vincent On 30/12/2024 00:19, Vincent Vanlaer wrot

Patch ping: [PATCH] c++: Fix ICE with #embed/RAW_DATA_CST after list conversion [PR118671]

Hi! On Tue, Jan 28, 2025 at 12:49:54AM +0100, Jakub Jelinek wrote: > The following testcases ICE with RAW_DATA_CSTs (so the first one since > introduction of #embed C++ optimizations and the latter since optimization > of large sequences of comma separated literals). > I've missed the fact that im

Re: [PING, PATCH] fortran: fix -MT/-MQ adding additional target [PR47485]

On 4/02/2025 01:42, Jerry D wrote: On 2/3/25 2:14 PM, Vincent Vanlaer wrote: Hi all, Gentle ping for the patch below: https://gcc.gnu.org/pipermail/ fortran/2024-December/061467.html Best wishes, Vincent On 30/12/2024 00:19, Vincent Vanlaer wrote: The -MT and -MQ options should replace

Re: [PING, PATCH] fortran: fix -MT/-MQ adding additional target [PR47485]

On 2/3/25 2:14 PM, Vincent Vanlaer wrote: Hi all, Gentle ping for the patch below: https://gcc.gnu.org/pipermail/ fortran/2024-December/061467.html Best wishes, Vincent On 30/12/2024 00:19, Vincent Vanlaer wrote: The -MT and -MQ options should replace the default target in the generated dep

Re: [PING, PATCH] fortran: fix -MT/-MQ adding additional target [PR47485]

Hi all, Gentle ping for the patch below: https://gcc.gnu.org/pipermail/fortran/2024-December/061467.html Best wishes, Vincent On 30/12/2024 00:19, Vincent Vanlaer wrote: The -MT and -MQ options should replace the default target in the generated dependency file. deps_add_target needs to be ca

[PING] [PATCH] testsuite: arm: Update expected RTL for reg_equal_test.c test

Gentle ping 🙂 Kind regards, Torbjörn On 2024-12-18 11:46, Torbjorn SVENSSON wrote: On 2024-12-12 15:50, Richard Earnshaw (lists) wrote: On 12/12/2024 13:36, Torbjorn SVENSSON wrote: On 2024-12-12 12:26, Richard Earnshaw (lists) wrote: On 10/11/2024 13:38, Torbjörn SVENSSON wrote: Hi Ric

Ping: [PATCH V2], Add PowerPC Dense Match Support for future cpus

Ping patches for adding intial dense math support to a potential future PowerPC processor: Explation of the patches: https://gcc.gnu.org/pipermail/gcc-patches/2024-December/670789.html Patch 1 of 3, add wD constraint: https://gcc.gnu.org/pipermail/gcc-patches/2024-December/670790.html Patch 2 of

Re: [ping,patch,avr] Try to work around PR118012 / PR118360

Georg-Johann Lay writes: > Ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-January/673336.html > > Am 11.01.25 um 14:09 schrieb Georg-Johann Lay: >> The patch below is for trunk. >> Andrew Pinski says he has a patch to fix it, bit that won't >> materialize >> before v16. >> AVR: PR118012

PING: [PATCH] asan: Fix missing FakeStack flag cleanup

On Thu, 2025-01-09 at 01:15 +0100, Ilya Leoshkevich wrote: > Bootstrapped and regtested on x86_64-redhat-linux.  Ok for master? > > > > The FakeStack flag is not zeroed out when can_store_by_pieces() > returns false.  Over time, this causes FakeStack::Allocate() to > perform > the maximum number

[ping,patch,avr] Try to work around PR118012 / PR118360

Ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-January/673336.html Am 11.01.25 um 14:09 schrieb Georg-Johann Lay: The patch below is for trunk. Andrew Pinski says he has a patch to fix it, bit that won't materialize before v16. AVR: PR118012 - Try to work around sick code from match.p

Re: [PING] [PATCH] testsuite: Fix test failing with -fimplicit-constexpr [PR118277]

On Mon, Jan 20, 2025 at 08:10:31PM +, Simon Martin wrote: > Successfully tested on x86_64-pc-linux-gnu with "make check-c++-all". > gcc/testsuite/ChangeLog: > > * g++.dg/cpp1z/constexpr-asm-5.C: Pass -fno-implicit-constexpr. LGTM. Jakub

Re: [PING] [PATCH] testsuite: Fix test failing with -fimplicit-constexpr [PR118277]

Hi Jakub, On 20 Jan 2025, at 10:28, Simon Martin wrote: > Hi Jakub, > > On 20 Jan 2025, at 10:15, Jakub Jelinek wrote: > >> On Mon, Jan 20, 2025 at 08:52:17AM +, Simon Martin wrote: >>> On 12 Jan 2025, at 12:10, Simon Martin wrote: >>> While testing an unrelated C++ patch with "make chec

[PING] [PATCH] c++: Don't ICE in build_class_member_access_expr during error recovery [PR118225]

Hi, On 4 Jan 2025, at 16:13, Simon Martin wrote: > The invalid case in this PR trips on an assertion in > build_class_member_access_expr that build_base_path would never return > an error_mark_node, which is actually incorrect if the object involves > a > tree with an error_mark_node DECL_INITIA

[PING] [PATCH] c++: Reinstate check for uninitialized bases with c++ <= 17 [PR118239]

Hi, On 3 Jan 2025, at 21:00, Simon Martin wrote: > We currently accept this code with c++ <= 17 even though it's invalid > since the base is not initialized (we properly reject it with c++ >= > 20) > > === cut here === > struct NoMut1 { int a, b; }; > struct NoMut3 : NoMut1 { > constexpr NoMut

Re: [PING] [PATCH] testsuite: Fix test failing with -fimplicit-constexpr [PR118277]

Hi Jakub, On 20 Jan 2025, at 10:15, Jakub Jelinek wrote: > On Mon, Jan 20, 2025 at 08:52:17AM +, Simon Martin wrote: >> On 12 Jan 2025, at 12:10, Simon Martin wrote: >> >>> While testing an unrelated C++ patch with "make check-c++-all", I >>> noticed that r15-6760-g38a13ea4117b96 added a test

Re: [PING] [PATCH] testsuite: Fix test failing with -fimplicit-constexpr [PR118277]

On Mon, Jan 20, 2025 at 08:52:17AM +, Simon Martin wrote: > On 12 Jan 2025, at 12:10, Simon Martin wrote: > > > While testing an unrelated C++ patch with "make check-c++-all", I > > noticed that r15-6760-g38a13ea4117b96 added a test case that fails > > with > > -fimplicit-constexpr. > > > > T

[PING] [PATCH] testsuite: Fix test failing with -fimplicit-constexpr [PR118277]

Hi, On 12 Jan 2025, at 12:10, Simon Martin wrote: > While testing an unrelated C++ patch with "make check-c++-all", I > noticed that r15-6760-g38a13ea4117b96 added a test case that fails > with > -fimplicit-constexpr. > > The problem is that this test unconditionally expects an error stating > t

Re: Ping [PATCH v3 0/3] Match: support additional cases of unsigned scalar arithmetic

On 12/17/24 5:00 AM, Akram Ahmad wrote: Pinging While this was submitted before the stage1 deadline, it seems to have fallen through the cracks on the review side. It's unfortunate, but I'd tend to think it ought to be deferred at this point until the gcc-16 cycle. However, I won't objec

Re: Ping: [PATCH] d,ada/spec: only sub nostd{inc,lib} rather than nostd{inc,lib}*

Excerpts from Arsen Arsenović's message of Oktober 7, 2024 11:31 pm: > Ping on this patch. > Thanks, this is OK for D. Note, that the gdc driver does try to accomodate for mixing C++ and D code in the same application - so given: gdc a.d b.cc It adds -lstdc++ to the link command for conve

[ping,patch 1/2] Add new target hook to assemble a variable

Ping for trunk https://gcc.gnu.org/pipermail/gcc-patches/2024-December/672050.html Notice that the patch is bootstrapped and reg-tested and I may commit-after-approval, so no further work from admins is needed. The avr part has already been approved 2024-12-20. The default action is an obvious

Re: [ping][PATCH] testsuite/118127: Pass fortran tests on ppc64le for IEEE128 long doubles

On 2025-01-06 11:34, Jakub Jelinek wrote: That looks incorrect to me. ppc_ieee128_ok just means that one can use the __ieee128 type (and only if -mfloat128 option is passed). What the tests care is whether real(16) is IEEE128 or IBM128. That is dependent on what glibc gcc has been configured agai

Re: [PING] [PATCH 1/6] Add tunables for input buffer

On Wed, Jan 08, 2025 at 07:47:27PM -0500, David Malcolm wrote: > On Wed, 2025-01-08 at 07:48 -0800, Andi Kleen wrote: > > > > I wanted to ping this patch series. Thanks. > > > > -Andi > > > > Thanks for tha patches, and sorry about not getting back to you earlier > (I've been focusing on analyz

Re: [PING] [PATCH 1/6] Add tunables for input buffer

On Wed, 2025-01-08 at 07:48 -0800, Andi Kleen wrote: > > I wanted to ping this patch series. Thanks. > > -Andi > Thanks for tha patches, and sorry about not getting back to you earlier (I've been focusing on analyzing many 100s of build failures with GCC 15 relative to GCC 14) Overall, the pat

[PING] [PATCH] c++: Suppress note linked to error suppressed by -Wno-template-body [PR118163]

Hi, On 21 Dec 2024, at 17:35, Simon Martin wrote: > When erroring out due to an incomplete type, we add a contextual note > about the type. However, when the error is suppressed by > -Wno-template-body, the note remains, making the compiler output quite > puzzling. > > This patch makes sure the n

[PING] [PATCH] c++: Avoid infinite recursion when deducing template arguments for invalid code [PR118078]

Hi, On 20 Dec 2024, at 20:56, Simon Martin wrote: > Hi, > > On 20 Dec 2024, at 20:37, Simon Martin wrote: > >> We currently fail due to "infinite recursion" on the following invalid >> code with -std=c++20 and above >> >> === cut here === >> template struct S { struct U { const S s; } u; }; >> S

[PING] [PATCH 1/6] Add tunables for input buffer

I wanted to ping this patch series. Thanks. -Andi

[PING] [PATCH] c++: Make sure fold_sizeof_expr returns the correct type [PR117775]

Hi, On 11 Dec 2024, at 22:27, Simon Martin wrote: > Hi, > > On 29 Nov 2024, at 15:33, Simon Martin wrote: > >> We currently ICE upon the following code, that is valid under >> -Wno-pointer-arith: >> >> === cut here === >> int main() { >> decltype( [](auto) { return sizeof(void); } ) x; >> ret

[PING] [PATCH] c++: Only prune capture proxies for constant variables at instantiation time [PR114292]

Hi, On 13 Dec 2024, at 13:50, Simon Martin wrote: > Hi Marek, > > On 13 Dec 2024, at 0:44, Marek Polacek wrote: > >> On Thu, Dec 12, 2024 at 07:07:38PM +, Simon Martin wrote: >>> We currently ICE upon the following valid (under -Wno-vla) code >>> >>> === cut here === >>> void f(int c) { >>>

[PING] [PATCH v8] c++: Fix overeager Woverloaded-virtual with conversion operators [PR109918]

Hi, On 11 Nov 2024, at 20:36, Simon Martin wrote: > Hi, > > On 30 Oct 2024, at 11:44, Simon Martin wrote: > >> Friendly ping. > Friendly ping. Ping. Thanks! Simon >> >> On 16 Oct 2024, at 17:43, Simon Martin wrote: >> >>> Hi Jason, >>> >>> On 12 Oct 2024, at 4:51, Jason Merrill wrote: >>> O

[PING] [PATCH] c++: Relax checking assert about elision to support -fno-elide-constructors [PR114619]

Hi, On 11 Nov 2024, at 20:35, Simon Martin wrote: > Hi, > > On 30 Oct 2024, at 11:46, Simon Martin wrote: > >> On 19 Oct 2024, at 11:09, Simon Martin wrote: >> >>> We currently ICE in checking mode with cxx_dialect < 17 on the >>> following >>> valid code >>> >>> === cut here === >>> struct X { >

Re: [ping][PATCH] testsuite/118127: Pass fortran tests on ppc64le for IEEE128 long doubles

On Mon, Jan 06, 2025 at 11:01:18AM -0500, Siddhesh Poyarekar wrote: > Ping! > > On 2024-12-19 08:16, Siddhesh Poyarekar wrote: > > Denormal behaviour is well defined for IEEE128 long doubles, so don't > > XFAIL some gfortran tests on ppc64le when configured with the IEEE128 > > long double ABI. >

[ping][PATCH] testsuite/118127: Pass fortran tests on ppc64le for IEEE128 long doubles

Ping! On 2024-12-19 08:16, Siddhesh Poyarekar wrote: Denormal behaviour is well defined for IEEE128 long doubles, so don't XFAIL some gfortran tests on ppc64le when configured with the IEEE128 long double ABI. gcc/testsuite/ChangeLog: PR testsuite/118127 * gfortran.dg/default_f

[PING][PATCH v2] Add new hardreg PRE pass

On Tue, Dec 17, 2024 at 11:53:24AM +, Andrew Carlotti wrote: > This pass is used to optimise assignments to the FPMR register in > aarch64. I chose to implement this as a middle-end pass because it > mostly reuses the existing RTL PRE code within gcse.cc. > > Compared to RTL PRE, the key diff

Ping: [PATCH] jit: Install jit headers in $(libsubincludedir) [PR 101491]

Hi, Gentle ping on this patch. Also, it would be nice if GCC installed libgccjit.pc to include the directory libgccjit headers and libraries are installed in correctly always. Currently, users of libgccjit have to assume GCC includes it in its include path always, but that might not be true if G

Re: [PING][PATCH 00/15] Fix data races with sub-longword accesses on Alpha

On Sun, 15 Dec 2024, Jeff Law wrote: > > Ping for: > > > > > > > >

Re: [PING][PATCH 00/15] Fix data races with sub-longword accesses on Alpha

On Sat, 14 Dec 2024, Jeff Law wrote: > > Ping for: > > > > > > > > (this will presumably need tweak

  1   2   3   4   5   6   7   8   9   10   >