[PATCH] loongarch: ignore zero-size fields in calling convention

Currently, LoongArch ELF psABI is not clear on the handling of zero- sized fields in aggregates arguments or return values [1]. The behavior of GCC trunk is puzzling considering the following cases: struct test1 { double a[0]; float x; }; struct test2 { float a[0]; float x; }; GCC trunk

[PATCH] cgraph: Fix up semantic_interposition handling [PR105306]

Hi! cgraph_node has a semantic_interposition flag which should mirror opt_for_fn (decl, flag_semantic_interposition). But it actually is initialized not from that, but from flag_semantic_interposition in the explicit symtab_node (symtab_type t) : type (t), resolution (LDPR_UNKNOWN), definit

回复：[PATCH] Asan changes for RISC-V.

Does Asan work for RISC-V currently? It seems that '-fsanitize=address' is still unsupported for RISC-V. If I add '--enable-libsanitizer' in Makefile.in to reconfigure, there are compiling errors. Is it because # libsanitizer not supported rv32, but it will break the rv64 multi-lib build, so we

Re: [PATCH] c++, coroutines: Avoid expanding within templates [PR103868]

On 4/18/22 15:49, Eric Gallager via Gcc-patches wrote: On Mon, Apr 18, 2022 at 10:01 AM Iain Sandoe via Gcc-patches wrote: From: Nathan Sidwell This is a forward-port of a patch by Nathan (against 10.x) which fixes an open PR. We are ICEing because we ended up tsubst_copying something that

Re: [PATCH] c++, coroutines: Improve check for throwing final await [PR104051].

On 4/18/22 11:34, Iain Sandoe wrote: We check that the final_suspend () method returns a sane type (i.e. a class or structure) but, unfortunately, that check has to be later than the one for a throwing case. If the user returns some nonsensical type from the method, we need to handle that in the

回复：[PATCH] Asan changes for RISC-V.

Does Asan work for RISC-V currently? It seems that '-fsanitize=address' is still unsupported for RISC-V. If I add '--enable-libsanitizer' in Makefile.in to reconfigure, there are compiling errors. Is it because # libsanitizer not supported rv32, but it will break the rv64 multi-lib build, so we

Re: [PATCH] c++, coroutines: Account for overloaded promise return_value() [PR105301].

On 4/18/22 10:03, Iain Sandoe wrote: Whether it was intended or not, it is possible to define a coroutine promise with multiple return_value() methods [which need not even have the same type]. We were not accounting for this possibility in the check to see whether both return_value and return_vo

Re: [PATCH] c++, coroutines: Make sure our temporaries are in a bind expr [PR105287]

On 4/18/22 10:02, Iain Sandoe wrote: There are a few cases where we can generate a temporary that does not need to be added to the coroutine frame (i.e. these are genuinely ephemeral). The intent was that unnamed temporaries should not be 'promoted' to coroutine frame entries. However there was

Re: Ping^2 [PATCH, rs6000] Correct match pattern in pr56605.c

Hi Segher, Yes, the old committed patch caused it matches two insns. So I submitted the new patch which fixes the problem. Here is the new patch. https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590958.html The new pattern is: /* { dg-final { scan-rtl-dump-times {\(compare:CC \(and:SI \(

Re: [PATCH] fold, simplify-rtx: Punt on non-representable floating point constants [PR104522]

> On Apr 14, 2022, at 1:53 AM, Richard Biener > wrote: > > On Wed, Apr 13, 2022 at 5:22 PM Qing Zhao wrote: >> >> Hi, Richard, >> >> Thanks a lot for taking a look at this issue (and Sorry that I haven’t fixed >> this one yet, I was distracted by other tasks then just forgot this one….) >>

Re: Ping^2 [PATCH, rs6000] Correct match pattern in pr56605.c

On Tue, Apr 19, 2022 at 04:05:06PM +0800, HAO CHEN GUI wrote: >I tested the test case on Linux and AIX with both big and little endian. > The test case requires lp64 target, so it won't be tested on 32-bit targets. > > On big endian (both AIX and Linux), it should match > (compare:CC (and:SI (

Re: [PATCH] PR fortran/104812: generate error for constuct-name clash with symbols

Hi Mike, for contributing, you'd need to have a GNU copyright assignment or DCO certification, and I cannot find your name in the usual place. See e.g. https://gcc.gnu.org/dco.html for details. Thanks, Harald Am 05.04.22 um 19:33 schrieb Mike Kashkarov via Gcc-patches: Greetings, Propose pa

Re: [PATCH] libgo: Fix non-portable sed commands

On Tue, Apr 19, 2022 at 11:06 AM Jonathan Wakely wrote: > > This fixes the libgo build if /usr/bin/sed is found before > /usr/xpg4/bin/sed on Solaris. > > Tested sparc-sun-solaris2.11, OK for trunk? Thanks, already committed based on your earlier e-mail. Ian

Re: Error when building gcc w/ Go language on Solaris

On Tue, Apr 19, 2022 at 6:36 AM Jonathan Wakely wrote: > > The 'check-tail' target in libgo/Makefile.am does: > > ... | sed -n -e 's/.* \(version.*$$\)/\1/p'` >> libgo.sum > > This doesn't work with Solaris sed (and is documented by Autoconf as > being non-portable). The $ needs to be outside the

Re: [PATCH, gcc-11 backport] gcov-profile: Allow negative counts of indirect calls [PR105282]

On 4/19/22 21:28, Sergei Trofimovich wrote: From: Sergei Trofimovich TOPN metrics are histograms that contain overall count and per-bucket count. Overall count can be negative when two profiles merge and some of per-bucket metrics are disacarded. I'm fine with that but I think, as we're close

[PATCH, gcc-11 backport] gcov-profile: Allow negative counts of indirect calls [PR105282]

From: Sergei Trofimovich TOPN metrics are histograms that contain overall count and per-bucket count. Overall count can be negative when two profiles merge and some of per-bucket metrics are disacarded. Noticed as an ICE on python PGO build where gcc crashes as: during IPA pass: modref

[PATCH] libsanitizer: asan: Always skip first object from dl_iterate_phdr

All platforms return the main executable as the first dl_phdr_info. FreeBSD, NetBSD, Solaris, and Linux-musl place the executable name in the dlpi_name field of this entry. It appears that only Linux-glibc uses the empty string. To make this work generically on all platforms, unconditionally skip

[PATCH] libgo: Fix non-portable sed commands

This fixes the libgo build if /usr/bin/sed is found before /usr/xpg4/bin/sed on Solaris. Tested sparc-sun-solaris2.11, OK for trunk? -- >8 -- Solaris sed does not allow '^' and '$' anchors inside groups, and does not support the '+' meta-character. ChangeLog: * libgo/Makefile.am (check

[PATCH] MAINTAINERS: Update my email address.

2022-04-19 Richard Henderson * MAINTAINERS: Update my email address. --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 30f81b3dd52..15973503722 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -53,7 +53,7 @@ aarch64 port

[PATCH v3] RISC-V: Add support for inlining subword atomic operations

RISC-V has no support for subword atomic operations; code currently generates libatomic library calls. This patch changes the default behavior to inline subword atomic calls (using the same logic as the existing library call). Behavior can be specified using the -minline-atomics and -mno-inline-a

[committed] sparc: Preserve ORIGINAL_REGNO in epilogue_renumber [PR105257]

Hi! The following testcase ICEs, because the pic register is (reg:DI 24 %i0 [109]) and is used in the delay slot of a return. We invoke epilogue_renumber and that changes it to (reg:DI 8 %o0) which no longer satisfies sparc_pic_register_p predicate, so we don't recognize the insn anymore. The fol

Re: [PATCH][v2] rtl-optimization/105231 - distribute_notes and REG_EH_REGION

On Tue, Apr 19, 2022 at 05:00:12PM +0200, Richard Biener wrote: > On Tue, 19 Apr 2022, Segher Boessenkool wrote: > > > > And that always is safe? Why do we have REG_EH_REGION for those cases > > > > at all, then? > > > > > > It's the only "safe" thing to do at distribute_notes time I think. If >

Re: [PATCH] c++: Fix up CONSTRUCTOR_PLACEHOLDER_BOUNDARY handling [PR105256]

On Tue, Apr 19, 2022, 6:53 AM Jakub Jelinek wrote: > On Mon, Apr 18, 2022 at 09:57:12AM -0400, Patrick Palka wrote: > > > Hmm, Patrick made a similar change and then reverted it for PR90996. > > > But it makes sense to me; when we replace placeholders, it's > appropriate > > > to look at the whol

Ping: [PATCH 0/2] avr: Add support AVR-DA and DB series devices

Ping patch. Link: https://gcc.gnu.org/pipermail/gcc-patches/2022-April/592668.html Thanks Joel Holdsworth

Re: [PATCH] maintainer-scripts: Adding GIT_CUSTOMREPO parameters to gcc_release script.

On Tue, 12 Apr 2022, Navid Rahimi via Gcc-patches wrote: > Hi GCC community, > > I need to have ability to point to custom repository in gcc_release > script. This small patch 1) does add a parameter "-g" to add custom The purpose of this script is for building official GCC releases, release

Re: [PATCH 0/4] Use pointer arithmetic for array references [PR102043]

On Sat, Apr 16, 2022 at 6:57 PM Mikael Morin via Gcc-patches wrote: > > Hello, > > this is a fix for PR102043, which is a wrong code bug caused by the > middle-end concluding from array indexing that the array index is > non-negative. This is a wrong assumption for "reversed arrays", > that is ar

Re: [PATCH][v2] rtl-optimization/105231 - distribute_notes and REG_EH_REGION

On Tue, 19 Apr 2022, Segher Boessenkool wrote: > On Tue, Apr 19, 2022 at 02:58:26PM +0200, Richard Biener wrote: > > On Tue, 19 Apr 2022, Segher Boessenkool wrote: > > The assert was for any landing pad which obviously failed - the > > testsuite fails were all for MUST_NOT_THROW (negative) regions

Re: [PATCH] Add condition coverage profiling

On 07/04/2022 14:04, Martin Liška wrote: > On 3/28/22 16:40, Jørgen Kvalsvik via Gcc-patches wrote: >> ... And with another tiny change that fixes Martin's while (1); case. > > Hello. > > Back to this ;) Thank you for the updated version of the patch. I have a > couple > of comments/requests: S

Re: [PATCH][v2] rtl-optimization/105231 - distribute_notes and REG_EH_REGION

On Tue, Apr 19, 2022 at 02:58:26PM +0200, Richard Biener wrote: > On Tue, 19 Apr 2022, Segher Boessenkool wrote: > The assert was for any landing pad which obviously failed - the > testsuite fails were all for MUST_NOT_THROW (negative) regions > which do not end basic-blocks. I see, thanks. > > >

Re: [PATCH][v2] rtl-optimization/105231 - distribute_notes and REG_EH_REGION

On Tue, 19 Apr 2022, Segher Boessenkool wrote: > Hi! > > So the assert last week was for a landing pad <= 0? < or =? The assert was for any landing pad which obviously failed - the testsuite fails were all for MUST_NOT_THROW (negative) regions which do not end basic-blocks. > On Tue, Apr 19, 2

回复：[PATCH] Asan changes for RISC-V.

Does Asan work for RISC-V currently? It seems that '-fsanitize=address' is still unsupported for RISC-V. If I add '--enable-libsanitizer' in Makefile.in to reconfigure, there are compiling errors. Is it because # libsanitizer not supported rv32, but it will break the rv64 multi-lib build, so we

Re: [AArch64] PR105162: emit barrier for __sync and __atomic builtins on CPUs without LSE

Hi Sebastian, > Wilco pointed out in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105162#c7​ > that > "Only __sync needs the extra full barrier, but __atomic does not." > The attached patch does that by adding out-of-line functions for > MEMMODEL_SYNC_*. > Those new functions contain a barrier o

Re: [PATCH][v2] rtl-optimization/105231 - distribute_notes and REG_EH_REGION

Hi! So the assert last week was for a landing pad <= 0? < or =? On Tue, Apr 19, 2022 at 01:02:09PM +0200, Richard Biener wrote: > The following mitigates a problem in combine distribute_notes which > places an original REG_EH_REGION based on only may_trap_p which is > good to test whether a non-

[PATCH] tree-optimization/104880 - move testcase

This renames the testcase to something picked up by the suites regexp. Tested on x86_64-unknown-linux-gnu, pushed. 2022-04-19 Richard Biener PR tree-optimization/104880 * g++.dg/opt/pr104880.C: Rename from pr104880.cc. --- gcc/testsuite/g++.dg/opt/{pr104880.cc => pr104880.C}

[x86_64 PATCH] PR middle-end/105135: Catch more cmov idioms in combine.

This patch addresses PR middle-end/105135, a missed-optimization regression affecting mainline. I agree with Jakub's comment that the middle-end optimizations are sound, reducing basic blocks and conditional expressions at the tree-level, but requiring backend's to recognize conditional move inst

Re: [PATCH] libstdc++: Add pretty printer for std::span

On Tue, 19 Apr 2022 at 12:33, Philipp Fent via Libstdc++ wrote: > > On 19.04.22 12:28, Jonathan Wakely wrote: > > Thanks, but we still need the DCO sign-off as I mailed about last week. > > Thanks for the clarification, your last mail didn't appear to have > content, so I might have missed that pa

Re: [PATCH] libstdc++: Add pretty printer for std::span

On 19.04.22 12:28, Jonathan Wakely wrote: Thanks, but we still need the DCO sign-off as I mailed about last week. Thanks for the clarification, your last mail didn't appear to have content, so I might have missed that part. I've now added my DCO sign-off. Best PhilippFrom 64b6779c2694f57981e

[PATCH][v2] tree-optimization/104912 - ensure cost model is checked first

The following makes sure that when we build the versioning condition for vectorization including the cost model check, we check for the cost model and branch over other versioning checks. That is what the cost modeling assumes, since the cost model check is the only one accounted for in the scalar

[PING] Re: [PATCH] tree-optimization/100810 - avoid undefs in IVOPT rewrites

On Fri, 1 Apr 2022, Richard Biener wrote: > The following attempts to avoid IVOPTs rewriting uses using > IV candidates that involve undefined behavior by using uninitialized > SSA names. First we restrict the set of candidates we produce > for such IVs to the original ones and mark them as not i

Re: [PATCH] gimple-fold: fix further missing stmt locations [PR104308]

On Thu, Apr 14, 2022 at 3:25 PM David Malcolm via Gcc-patches wrote: > > PR analyzer/104308 initially reported about a > -Wanalyzer-use-of-uninitialized-value diagnostic using UNKNOWN_LOCATION > when complaining about certain memmove operations where the source > is uninitialized. > > In r12-7856-

[PATCH][v2] rtl-optimization/105231 - distribute_notes and REG_EH_REGION

The following mitigates a problem in combine distribute_notes which places an original REG_EH_REGION based on only may_trap_p which is good to test whether a non-call insn can possibly throw but not if actually it does or we care. That's something we decided at RTL expansion time where we possibly

[committed] libstdc++: Fix syntax error in libbacktrace configuration

Tested x86_64-linux, pushed to trunk. -- >8 -- Using == instead of = causes a configuration error with dash as the shell: checking whether to build libbacktrace support... /home/devel/building/work/src/gcc-12-20220417/libstdc++-v3/configure: 77471: test: auto: unexpected operator /home/devel/b

Re: [PATCH] c++: Fix up CONSTRUCTOR_PLACEHOLDER_BOUNDARY handling [PR105256]

On Mon, Apr 18, 2022 at 09:57:12AM -0400, Patrick Palka wrote: > > Hmm, Patrick made a similar change and then reverted it for PR90996. > > But it makes sense to me; when we replace placeholders, it's appropriate > > to look at the whole aggregate initialization rather than the innermost > > CONSTR

Re: [PATCH] libstdc++: Stop defining _GLIBCXX_ASSERTIONS in floating_to_chars.cc

On Thu, 14 Apr 2022 at 20:48, Patrick Palka via Libstdc++ wrote: > > Assertions were originally enabled in the compiled-in floating-point > std::to_chars implementation to help shake out any bugs, but they > apparently impose a significant performance penalty, in particular for > the hex formattin

Re: [PATCH] libstdc++: Update incorrect statement about mainline in docs

On Tue, 19 Apr 2022 at 08:01, Richard Biener wrote: > > On Thu, 14 Apr 2022, Jonathan Wakely wrote: > > > On Thu, 14 Apr 2022 at 11:55, Richard Biener wrote: > > > > > > On Thu, 14 Apr 2022, Jonathan Wakely wrote: > > > > > > > On Thu, 14 Apr 2022 at 11:36, Richard Biener wrote: > > > > > > > >

Re: [PATCH] libstdc++: Add pretty printer for std::span

On Tue, 19 Apr 2022 at 10:34, Philipp Fent wrote: > > On 04.04.22 13:39, Jonathan Wakely wrote: > > Nice, thanks. I'll get this committed in time for GCC 12 (and backport > > it to release branches too). > > I've attached a rebased patch for trunk and tested it on x86_64-linux. > I also backported

FW: [PATCH] PR fortran/104812: generate error for constuct-name clash with symbols

0001-Fortran-add-error-for-constuct-name-conflicts-with-s.patch Description: Binary data rcptInfo.txt Description: Binary data

Re: [PATCH] c++, coroutines: Avoid expanding within templates [PR103868]

On 4/18/22 21:55, Iain Sandoe wrote: IIRC the original code takes a few minutes to compile on my laptop, so i’d expect it might be very time-consuming to do - perhaps Martin has some ideas? Yes, the original testcase is huge to reduce and I'm not willing to waste time on it. That said, I wou

Re: [PATCH] gcov-profile: Allow negavive counts of indirect calls [PR105282]

Hi. Thanks you for the patch, please apply it. Cheers, Martin

Re: [PATCH] libstdc++: Add pretty printer for std::span

On 04.04.22 13:39, Jonathan Wakely wrote: Nice, thanks. I'll get this committed in time for GCC 12 (and backport it to release branches too). I've attached a rebased patch for trunk and tested it on x86_64-linux. I also backported it for the release branches, gcc-11 tests also pass, on gcc-10

Re: [PATCH] PR105169 Fix references to discarded sections

On Thu, 14 Apr 2022, Giuliano Belinassi wrote: > When -fpatchable-function-entry= is enabled, certain C++ codes fails to > link because of generated references to discarded sections in > __patchable_function_entry section. This commit fixes this problem by > puting those references in a COMDAT sec

Re: Ping^2 [PATCH, rs6000] Correct match pattern in pr56605.c

Hi, I tested the test case on Linux and AIX with both big and little endian. The test case requires lp64 target, so it won't be tested on 32-bit targets. On big endian (both AIX and Linux), it should match (compare:CC (and:SI (subreg:SI (reg:DI 207) 4) On little endian (both AIX and Linux), it

Re: [pushed] libgccjit: Fix a bootstrap break for some targets.

On Thu, Apr 14, 2022 at 9:19 PM Iain Sandoe via Gcc-patches wrote: > > Some targets use 'long long unsigned int' for unsigned HW int, and this > leads to a Werror=format= fail for two print cases in jit-playback.cc > introduced in r12-8117-g30f7c83e9cfe (Add support for bitcasts [PR104071]) > > As

Re: [PATCH] doc/invoke.texi: CRIS: Remove references to cris-axis-linux-gnu

On Mon, Apr 18, 2022 at 6:51 PM Hans-Peter Nilsson wrote: > > I'm about to commit this to master. > > I'd like to also install this on the gcc-11 branch. > > Ok? OK. > -- 8< -- > > ...and related options. These stale bits were overlooked when support > for "Linux/GNU" and CRIS v32 was removed,

Re: [PATCH] doc/install.texi: CRIS: Remove gone websites. Adjust CRIS targets

On Mon, Apr 18, 2022 at 6:48 PM Hans-Peter Nilsson wrote: > > I'm about to commit this to master. > > I'd like to also install this on the gcc-11 branch. OK. > Ok? OK. > -- 8< -- > > That is, support for cris-linux-gnu was removed in gcc-11, but > install.texi wasn't adjusted accordingly. Als

Re: [PATCH] testsuite: Skip target not support -pthread [pr104676].

On Tue, 19 Apr 2022, jiawei wrote: > The "ftree-parallelize-loops=" imply -pthread option in gcc/gcc.cc, > some target are not support pthread like elf target use newlib, > and will get an error: > > "*-*-elf-gcc: error: unrecognized command-line option '-pthread'" > > so we add an additional co

Re: [PATCH] libstdc++: Update incorrect statement about mainline in docs

On Thu, 14 Apr 2022, Jonathan Wakely wrote: > On Thu, 14 Apr 2022 at 11:55, Richard Biener wrote: > > > > On Thu, 14 Apr 2022, Jonathan Wakely wrote: > > > > > On Thu, 14 Apr 2022 at 11:36, Richard Biener wrote: > > > > > > > > On Thu, 14 Apr 2022, Jonathan Wakely wrote: > > > > > > > > > This f

Re: [PATCH] tree-optimization/104010 - fix SLP scalar costing with patterns

On Thu, 14 Apr 2022, Richard Sandiford wrote: > Richard Biener writes: > > On Thu, 14 Apr 2022, Richard Sandiford wrote: > > > >> Richard Biener writes: > >> > When doing BB vectorization the scalar cost compute is derailed > >> > by patterns, causing lanes to be considered live and thus not > >