Re: [PATCH] c++: set loc on call even if result is discarded

On Fri, Apr 8, 2022 at 12:49 AM Alexandre Oliva via Gcc-patches wrote: > > On Apr 6, 2022, Jason Merrill wrote: > > > On 4/6/22 15:37, Alexandre Oliva wrote: > > Need to adjust this subject line, as well. > > *nod*, thanks > > >> * tree.cc (protected_set_expr_location): Propagate locus to > >> c

Re: [PATCH 0/3] Fix PR debug/105089

On Thu, Apr 7, 2022 at 9:42 PM Indu Bhagat via Gcc-patches wrote: > > ping The series is OK > On 3/30/22 4:31 PM, Indu Bhagat wrote: > > Hello, > > > > This patch set fixes PR debug/105089. > > > > [PS: The first patch in the series "ctfc: get rid of the static variable in > > ctf_list_add_ctf_v

Re: [PATCH] tree-optimization/105175 - avoid -Wvector-operation-performance

On Thu, 7 Apr 2022, Martin Sebor wrote: > On 4/7/22 00:59, Richard Biener wrote: > > On Wed, 6 Apr 2022, Martin Sebor wrote: > > > >> On 4/6/22 03:23, Richard Biener wrote: > >>> This avoids -Wvector-operation-performance diagnostics for vectorizer > >>> produced code. It's unfortunate the warni

Re: [PATCH] libgcc: IA64: don't compile glibc-based unwinder without libc headers

On Thu, Apr 7, 2022 at 6:13 PM Sergei Trofimovich via Gcc-patches wrote: > > From: Sergei Trofimovich > > In --without-headers mode gcc fails to bootstrap on libgcc as: > > /build/build/./gcc/xgcc -B/build/build/./gcc/ ... -Dinhibit_libc -c > fde-glibc.c > ../../../gcc-12-20220403/libgcc

Re: [PATCH v2] RISCV: Add support for inlining subword atomics

Hi Patrick, Glad to know that efforts have been made to add inlining subword atomic supports into gcc. The patch looks great so far, yet as Andreas Schwab has pointed out (at riscv-collab/riscv-gcc#337), looks like it only contains atomic fetch stuff. Just wondering do you have further plans t

Re: [PATCH] rs6000: Guard bifs {un, }pack_{longdouble, ibm128} under hard float [PR103623]

Hi Segher & Jakub, Thanks for the comments! on 2022/4/7 9:00 PM, Jakub Jelinek wrote: > On Thu, Apr 07, 2022 at 06:09:52AM -0500, Segher Boessenkool wrote: >> Hi! >> >> On Thu, Mar 03, 2022 at 10:11:32AM +0800, Kewen.Lin wrote: >>> As PR103623 shows, it's a regression failure due to new built-in

New German PO file for 'gcc' (version 12.1-b20220403)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'gcc' has been submitted by the German team of translators. The file is available at: https://translationproject.org/latest/gcc/de.po (This file, 'gcc-12.1-b20220403.de.po',

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

Hi, Gentle ping this: https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590958.html Thanks On 15/3/2022 上午 10:06, HAO CHEN GUI wrote: > Hi, > Gentle ping this: > https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590958.html > Thanks > > On 28/2/2022 上午 11:17, HAO CHEN GUI wro

[PATCH, V3] Eliminate power8 fusion options, use power8 tuning, PR target/102059

Eliminate power8 fusion options, use power8 tuning, PR target/102059 This is V3 of the patch. Compared to V2 of the patch, it changed some of the comments based on the feedback. Since -mpower8-fusion-sign was an undocumented option, I removed some of the wording about its removal. I removed an o

Re: [PATCH] c++: set loc on call even if result is discarded

On Apr 6, 2022, Jason Merrill wrote: > On 4/6/22 15:37, Alexandre Oliva wrote: > Need to adjust this subject line, as well. *nod*, thanks >> * tree.cc (protected_set_expr_location): Propagate locus to >> call wrapped in cast-to-void. > I'm reluctant to put this C++-specific change in a simple

Committed: [PATCH] Disable float128 tests on VxWorks, PR target/104253.

This is the patch that I committed. I will do the backport in a few days to GCC 11 and 10. Disable float128 tests on VxWorks, PR target/104253. In PR target/104253, it was pointed out the that test case added as part of fixing the PR does not work on VxWorks because float128 is not supported on

libgomp nvptx plugin: Split 'PLUGIN_NVPTX_DYNAMIC' into 'PLUGIN_NVPTX_INCLUDE_SYSTEM_CUDA_H' and 'PLUGIN_NVPTX_LINK_LIBCUDA' (was: [PATCH] Allow building GCC with PTX offloading even without CUDA bein

Hi! On 2017-01-13T19:11:23+0100, Jakub Jelinek wrote: > Especially for distributions it is undesirable to need to have proprietary > CUDA libraries and headers installed when building GCC. > --- libgomp/plugin/configfrag.ac.jj 2017-01-13 12:07:56.0 +0100 > +++ libgomp/plugin/configfrag

Re: [PATCH] c++: tolerate cdtors returning this in constexpr

Hello, Jason, On Apr 6, 2022, Jason Merrill wrote: > On 4/6/22 15:36, Alexandre Oliva wrote: > Please adjust your patch subject lines for the new guidelines adopted > as part of the git transition: > https://gcc.gnu.org/contribute.html#patches Oh, wow, I had missed those guidelines entirely!

Re: [PATCH] Disable float128 tests on VxWorks, PR target/104253.

Hi! On Thu, Apr 07, 2022 at 02:59:55PM -0400, Michael Meissner wrote: > On Thu, Apr 07, 2022 at 06:00:51AM -0500, Segher Boessenkool wrote: > > On Thu, Apr 07, 2022 at 12:29:45AM -0400, Michael Meissner wrote: > > > In PR target/104253, it was pointed out the that test case added as part > > > of

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

Hi, With -moutline-atomics gcc stops generating a barrier for __sync builtins: https://gcc.gnu.org/PR105162 This is a problem on CPUs without LSE instructions where the ld/st exclusives do not guarantee a full barrier. The attached patch ad

Re: [PATCH 0/3] Fix PR debug/105089

ping On 3/30/22 4:31 PM, Indu Bhagat wrote: Hello, This patch set fixes PR debug/105089. [PS: The first patch in the series "ctfc: get rid of the static variable in ctf_list_add_ctf_vars" is unrelated to the PR and is combined here only for ease of review.] As noted in the PR debug/105089, gc

Re: [PATCH] rs6000/test: Adjust p9-vec-length-7 sensitive to unroll [PR103196]

Hi! On Thu, Apr 07, 2022 at 09:19:51AM -0500, will schmidt wrote: > On Mon, 2022-02-28 at 13:37 +0800, Kewen.Lin via Gcc-patches wrote: > > As PR103196 shows, p9-vec-length-full-7.c needs to be adjusted as the > > complete unrolling can happen on some of its loops. This patch is to > > use pragma

Re: [PATCH] Pass PKG_CONFIG_PATH down from top-level Makefile

Ping. On 2022-03-29 16:04, Simon Marchi wrote: > Ping! > > On 2022-03-15 17:26, Simon Marchi wrote: >> From: Simon Marchi >> >> [Sending to binutils, gdb-patches and gcc-patches, since it touches the >> top-level Makefile/configure] >> >> I have my debuginfod library installed in a non-standard

Re: [PATCH] Disable float128 tests on VxWorks, PR target/104253.

On Thu, Apr 07, 2022 at 12:47:27PM +0200, Eric Botcazou wrote: > > I have run the tests on my usual Linux systems (little endian power10, > > little endian power9, big endian power8), but I don't have access to a > > VxWorks system. Eric does this fix the failure for you? > > Yes, if you add '*'

Re: [PATCH] Disable float128 tests on VxWorks, PR target/104253.

On Thu, Apr 07, 2022 at 06:00:51AM -0500, Segher Boessenkool wrote: > On Thu, Apr 07, 2022 at 12:29:45AM -0400, Michael Meissner wrote: > > In PR target/104253, it was pointed out the that test case added as part > > of fixing the PR does not work on VxWorks because float128 is not > > supported on

[PATCH][committed] testsuite: delete slp scan from loop vect test.

Hi All, I accidentally left in an slp1 check in the vect test which showed up as UNRESOLVED and had missed it in the sum file. This deletes that line. Committed under obvious rule. Thanks, Tamar gcc/testsuite/ChangeLog: PR testsuite/105196 * gcc.dg/vect/complex/fast-math-compl

[PATCH v1] libstdc++: Default to mutex-based atomics on RISC-V

The RISC-V port requires libatomic to be linked in order to resolve various atomic functions, which results in builds that have "--with-libstdcxx-lock-policy=auto" defaulting to mutex-based locks. Changing this to direct atomics breaks the ABI, this forces the auto detection mutex-based atomics on

[RFC 7/7] RISCV: Relax mem_thread_fence

This change brings atomic fences in line with table A.6 of the ISA manual. Relax mem_thread_fence according to the memmodel given. 2022-03-31 Patrick O'Neill * riscv.cc: Expose helper functions to sync.md. * riscv-protos.h: Likewise. * sync.md (mem_thread_fence_1): Chang

[RFC 6/7] RISCV: Optimize Atomic Stores

This change brings atomic stores in line with table A.6 of the ISA manual. 2022-03-31 Patrick O'Neill PR target/89835 * riscv.cc (atomic_cas_value_strong): Add %I flag for atomic store fences. * sync.md (atomic_store): Use simple store instruction in combi

[RFC 5/7] RISCV: Optimize LR/SC Pairs

Introduce the %I and %J flags for setting the .aqrl bits on LR/SC pairs as needed. Atomic compare and exchange ops provide 2 types of memory models. C++17 and later places no restrictions on the relative strength of each model, so ensure we cover both by using a model that enforces the ordering of

[RFC 4/7] RISCV: Optimize AMO Ops

Atomic operations with the appropriate bits set already enfore release semantics. Remove unnecessary release fences from atomic ops. This change brings amo ops in line with table A.6 of the ISA manual. 2022-03-31 Patrick O'Neill * riscv.cc (riscv_memmodel_needs_amo_acquire): Change func

[RFC 3/7] RISCV: Add AMO release bits

This patch sets the relevant .rl bits on amo operations. 2022-03-31 Patrick O'Neill * riscv.cc (riscv_print_operand): change behavior of %A to include release bits. Signed-off-by: Patrick O'Neill --- gcc/config/riscv/riscv.cc | 7 ++- 1 file changed, 6 insertions(+), 1 del

[RFC 2/7] RISCV: Enforce Atomic Compare Exchange SEQ_CST

This patch enforces SEQ_CST for atomic compare_exchange ops. Replace Fence/LR.aq/SC.aq pairs with strong SEQ_CST LR.aqrl/SC.rl pairs recommended by table A.6 of the ISA manual. 2022-03-31 Patrick O'Neill * sync.md: Change LR.aq/SC.rl pairs into sequentially consistent LR.aqrl/SC

[RFC 1/7] RISCV: Enforce Libatomic LR/SC SEQ_CST

Replace LR.aq/SC.rl pairs with the SEQ_CST LR.aqrl/SC.rl pairs recommended by table A.6 of the ISA manual. 2022-03-31 Patrick O'Neill * atomic.c: Change LR.aq/SC.rl pairs into sequentially consistent LR.aqrl/SC.rl pair. Signed-off-by: Patrick O'Neill --- libgcc/config/riscv/at

[RFC 0/7] RISCV: Implement ISA Manual Table A.6 Mappings

This series should not be applied as it causes an ABI break. This RFC aims to bring the RISCV atomics implementation in line with the recommended mapping present in table A.6 of the ISA manual. https://github.com/riscv/riscv-isa-manual/blob/c7cf84547b3aefacab5463add1734c1602b67a49/src/memory.tex#

Re: [PATCH] tree-optimization/105175 - avoid -Wvector-operation-performance

On 4/7/22 00:59, Richard Biener wrote: On Wed, 6 Apr 2022, Martin Sebor wrote: On 4/6/22 03:23, Richard Biener wrote: This avoids -Wvector-operation-performance diagnostics for vectorizer produced code. It's unfortunate the warning_at code in tree-vect-generic.cc needs adjustments but the dia

[AArch64] PR target/105157 Increase number of cores TARGET_CPU_DEFAULT can encode

Hi, This addresses the compile-time increase seen in the PR target/105157. This was being caused by selecting the wrong core tuning, as when we added the latest AArch64 the TARGET_CPU_generic tuning was pushed beyond the 0x3f mask we used to encode both target cpu and attributes into TARGET_C

Re: [PATCH] Add condition coverage profiling

Hello Jørgen, there could be an issue with conditions in for loops: 3: 189: for (int a = 0; a <= 1; ++a) { branch 0 taken 2 branch 1 taken 1 (fallthrough) conditions covered 0/2 condition 0 not covered (true) condition 0 not covered (false) -- embedded brains GmbH Herr Sebastian H

Re: [PATCH] fold-const: Fix up make_range_step [PR105189]

> Am 07.04.2022 um 17:47 schrieb Jakub Jelinek via Gcc-patches > : > > Hi! > > The following testcase is miscompiled, because fold_truth_andor > incorrectly folds > (unsigned) foo () >= 0U && 1 > into > foo () >= 0 > For the unsigned comparison (which is useless in this case, > as >= 0U is a

[PATCH] libgcc: IA64: don't compile glibc-based unwinder without libc headers

From: Sergei Trofimovich In --without-headers mode gcc fails to bootstrap on libgcc as: /build/build/./gcc/xgcc -B/build/build/./gcc/ ... -Dinhibit_libc -c fde-glibc.c ../../../gcc-12-20220403/libgcc/config/ia64/fde-glibc.c:33:10: fatal error: stdlib.h: No such file or directory

Re: [PATCH] c: Error on va_arg with function type [PR105149]

On Thu, Apr 07, 2022 at 05:52:53PM +0200, Jakub Jelinek wrote: > Hi! > > In the PR Joseph said that the C standard for va_arg talks about > pointers to object type and as a function type is not object type, > it is invalid. > > The following patch diagnoses it in the FE, instead of ICEing later o

[PATCH] c: Error on va_arg with function type [PR105149]

Hi! In the PR Joseph said that the C standard for va_arg talks about pointers to object type and as a function type is not object type, it is invalid. The following patch diagnoses it in the FE, instead of ICEing later on when optimizations are turned on (and with -O0 doing something weird at run

[PATCH] fold-const: Fix up make_range_step [PR105189]

Hi! The following testcase is miscompiled, because fold_truth_andor incorrectly folds (unsigned) foo () >= 0U && 1 into foo () >= 0 For the unsigned comparison (which is useless in this case, as >= 0U is always true, but hasn't been folded yet), previous make_range_step derives exp (unsigned) foo

Re: [PATCH]AArch64 fix ls64 intrinsics expansion [PR104409]

Tamar Christina writes: > Hi All, > > The LS64 intrinsics used a machinery that's not safe to use unless being > called from a pragma instantiation. > > This moves the initialization code to a new pragma for arm_acle.h. > > Bootstrapped Regtested on aarch64-none-linux-gnu and no issues. > > I didn

Re: [PATCH] Disable float128 tests on VxWorks, PR target/104253.

On Thu, Apr 07, 2022 at 08:50:53AM -0500, will schmidt wrote: > On Thu, 2022-04-07 at 06:00 -0500, Segher Boessenkool wrote: > > On Thu, Apr 07, 2022 at 12:29:45AM -0400, Michael Meissner wrote: > > > In PR target/104253, it was pointed out the that test case added as part > > > of fixing the PR do

[PATCH]AArch64 fix ls64 intrinsics expansion [PR104409]

Hi All, The LS64 intrinsics used a machinery that's not safe to use unless being called from a pragma instantiation. This moves the initialization code to a new pragma for arm_acle.h. Bootstrapped Regtested on aarch64-none-linux-gnu and no issues. I didn't add the testcase from the PR as it's 6

Re: [PATCH] rs6000/test: Adjust p9-vec-length-7 sensitive to unroll [PR103196]

On Mon, 2022-02-28 at 13:37 +0800, Kewen.Lin via Gcc-patches wrote: > Hi, > > As PR103196 shows, p9-vec-length-full-7.c needs to be adjusted as the > complete unrolling can happen on some of its loops. This patch is to > use pragma "GCC unroll 0" to disable all possible loop unrollings. > Hope it

Re: [committed][nvptx] Fix ASM_SPEC workaround for sm_30

Hi! On 2022-03-31T09:40:47+0200, Tom de Vries via Gcc-patches wrote: > Newer versions of CUDA no longer support sm_30, and nvptx-tools as > currently doesn't handle that gracefully when verifying > ( https://github.com/MentorEmbedded/nvptx-tools/issues/30 ). There's now

Re: [PATCH] Improve profile handling in switch lowering.

PING^3 On 3/24/22 11:22, Martin Liška wrote: PING^2 On 3/4/22 14:47, Martin Liška wrote: PING^1 On 1/26/22 12:11, Martin Liška wrote: Hello. Right now, switch lowering does not update basic_block::count values so that they are uninitiliazed. Moreover, I've updated probability scaling when a

Re: [PATCH] Disable float128 tests on VxWorks, PR target/104253.

On Thu, 2022-04-07 at 06:00 -0500, Segher Boessenkool wrote: > On Thu, Apr 07, 2022 at 12:29:45AM -0400, Michael Meissner wrote: > > In PR target/104253, it was pointed out the that test case added as part > > of fixing the PR does not work on VxWorks because float128 is not > > supported on that s

Re: [PATCH v2] rs6000: Adjust mov optabs for opaque modes [PR103353]

On Thu, 2022-04-07 at 17:29 +0800, Kewen.Lin wrote: > Hi, > > As PR103353 shows, we may want to continue to expand a MMA built-in > function like a normal function, even if we have already emitted > error messages about some missing required conditions. As shown in > that PR, without one explicit

Re: Fix wrong code in gnatmake

On Thu, 7 Apr 2022, Jan Hubicka wrote: > > On Thu, 7 Apr 2022, Jan Hubicka wrote: > > > > > Hi, > > > this patch fixes miscompilation of gnatmake. Modref attempts to track > > > memory > > > accesses relative to the base pointers which are parameters of functions. > > > If it fails, it still ma

Re: [PATCH] rs6000: Guard bifs {un, }pack_{longdouble, ibm128} under hard float [PR103623]

On Thu, Apr 07, 2022 at 06:09:52AM -0500, Segher Boessenkool wrote: > Hi! > > On Thu, Mar 03, 2022 at 10:11:32AM +0800, Kewen.Lin wrote: > > As PR103623 shows, it's a regression failure due to new built-in > > function framework, previously we guard __builtin_{un,}pack_{longdouble, > > ibm128} bui

Re: Fix wrong code in gnatmake

> On Thu, 7 Apr 2022, Jan Hubicka wrote: > > > Hi, > > this patch fixes miscompilation of gnatmake. Modref attempts to track > > memory > > accesses relative to the base pointers which are parameters of functions. > > If it fails, it still makes difference between unknown memory access and > > g

[committed] analyzer: fix leak false +ve with symbolic writes [PR102308]

(I typoed 102308 as 102208 in a few places when I committed; I've fixed them in this email, but in particular the subject line in what I pushed to git has the wrong ID; it should be 102308). PR analyzer/102308 reports false positives from -Wanalyzer-malloc-leak. The root cause is the analyzer gett

Re: [PATCH] toplev: use HOST_WIDE_INT for local_tick to prevent overflow

Hi Richard, The gcc devs have apparently declined to do anything about this bug (it's marked as "RESOLVED WONTFIX") and don't care much about plugins I guess: , so I won't be sending a v2. However, On Thu, Apr 7, 2022 at 8:30 AM Richard Biener

Re: Fix wrong code in gnatmake

On Thu, 7 Apr 2022, Jan Hubicka wrote: > Hi, > this patch fixes miscompilation of gnatmake. Modref attempts to track memory > accesses relative to the base pointers which are parameters of functions. > If it fails, it still makes difference between unknown memory access and > global memory access

Re: [PATCH] Add condition coverage profiling

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: 1) I noticed the following cannot be linked: $ cat erro

Re: Fix pure/const propagation in modref

> On Thu, Apr 7, 2022 at 1:20 PM Jan Hubicka via Gcc-patches > wrote: > > > > Hi, > > this patch fixes ipa-modref propagation of pure/const functions. When we > > inline > > function, the modref summary is updated to represent the function after > > inlining and there we need to propagate nondet

Fix wrong code in gnatmake

Hi, this patch fixes miscompilation of gnatmake. Modref attempts to track memory accesses relative to the base pointers which are parameters of functions. If it fails, it still makes difference between unknown memory access and global memory access. The second makes it possible to disambiguate wi

Re: Fix pure/const propagation in modref

On Thu, Apr 7, 2022 at 1:20 PM Jan Hubicka via Gcc-patches wrote: > > Hi, > this patch fixes ipa-modref propagation of pure/const functions. When we > inline > function, the modref summary is updated to represent the function after > inlining and there we need to propagate nondeterministic and s

Fix pure/const propagation in modref

Hi, this patch fixes ipa-modref propagation of pure/const functions. When we inline function, the modref summary is updated to represent the function after inlining and there we need to propagate nondeterministic and side-effects flag. Bootstrapped/regtested x86_64-linux, will commit it shortly.

Re: [PATCH] rs6000: Guard bifs {un, }pack_{longdouble, ibm128} under hard float [PR103623]

Hi! On Thu, Mar 03, 2022 at 10:11:32AM +0800, Kewen.Lin wrote: > As PR103623 shows, it's a regression failure due to new built-in > function framework, previously we guard __builtin_{un,}pack_{longdouble, > ibm128} built-in functions under hard float, so they are unavailable > with the given confi

Re: [PATCH] Disable float128 tests on VxWorks, PR target/104253.

On Thu, Apr 07, 2022 at 12:29:45AM -0400, Michael Meissner wrote: > In PR target/104253, it was pointed out the that test case added as part > of fixing the PR does not work on VxWorks because float128 is not > supported on that system. I have modified the three tests for float128 so > that they a

Re: [PATCH] Disable float128 tests on VxWorks, PR target/104253.

> I have run the tests on my usual Linux systems (little endian power10, > little endian power9, big endian power8), but I don't have access to a > VxWorks system. Eric does this fix the failure for you? Yes, if you add '*' at the end of the selector, i.e. [istarget *-*-vxworks*]. > If it does f

PING^2 [PATCH] rs6000/test: Adjust p9-vec-length-7 sensitive to unroll [PR103196]

Hi, Gentle ping: https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590959.html This patch is to fix one regressed test case, I guess it still can be considered for stage 4. BR, Kewen > on 2022/2/28 1:37 PM, Kewen.Lin via Gcc-patches wrote: >> Hi, >> >> As PR103196 shows, p9-vec-length-fu

[PATCH][GCC11] tree-optimization/99121 - avoid ICEing for non-constant sizes

The following is a simple fix to avoid ICEing on non-constant sizes of ARRAY_REFs instead of backporting too intrusive changes done on trunk. Bootstrap / regtest pending on x86_64-unknown-linux-gnu. 2022-04-07 Richard Biener PR tree-optimization/99121 * gimple-array-bounds.cc

Re: [PATCH] rs6000: Adjust mov optabs for opaque modes [PR103353]

on 2022/4/2 5:52 AM, Peter Bergner wrote: > On 4/1/22 3:50 PM, will schmidt wrote: >> Is there a testcase, new or existing, that illustrates this error path? > > Well, the already existsing test case pr101849.c is where the issue was seen, > but only when compiled by hand outside of the test harne

[PATCH v2] rs6000: Adjust mov optabs for opaque modes [PR103353]

Hi, As PR103353 shows, we may want to continue to expand a MMA built-in function like a normal function, even if we have already emitted error messages about some missing required conditions. As shown in that PR, without one explicit mov optab on OOmode provided, it would call emit_move_insn recu

Re: [RFC/gcov 00/12] Add merge-stream subcommand to gcov-tool

Hello Martin, thanks for the review. I am not really used to write func (). On 07/04/2022 10:38, Martin Liška wrote: TODO: * Documentation I would install the patches with documentation change bits. Ok, I will add some documentation changes and send them with a v2 of the patch set after

GCC 11.2.1 Status Report (2022-04-07)

Status == The gcc-11 branch is in regression and documentation fixing mode. It's time to prepare for the release of GCC 11.3 as we have accumulated quite a number of fixes since GCC 11.2 was released. The plan is to create a release candidate on Wednesday, April 13th, which is in about one

Re: [RFC/gcov 00/12] Add merge-stream subcommand to gcov-tool

On 3/31/22 13:35, Sebastian Huber wrote: This patch set is a proof of concept. The aim is to better support gcov in free-standing environments. For example, you can run a test executable which dumps all gcov info objects in a serial data stream using __gcov_info_to_gcda() and the new __gcov_file

Re: [RFC/gcov 12/12] gcov-tool: Add merge-stream subcommand

On 3/31/22 13:35, Sebastian Huber wrote: gcc/ * gcov-tool.cc (gcov_profile_merge_stream): Declare. (print_merge_stream_usage_message): New. (merge_stream_usage): Likewise. (do_merge_stream): Likewise. (print_usage): Call print_merge_stream_usage_message().

Re: [RFC/gcov 11/12] gcov: Record EOF error during read

On 3/31/22 13:35, Sebastian Huber wrote: |+enum gcov_file_error {| Please put the brace to the next line and comment the enum type. Martin

Re: [RFC/gcov 08/12] gcov: Move prepend to list to read_gcda_file()

On 3/31/22 13:35, Sebastian Huber wrote: |+ /* Prepend to gcov info list */| Please add dot and 2 spaces. Martin

Re: [RFC/gcov 06/12] gcov-tool: Support file input from stdin

On 3/31/22 13:35, Sebastian Huber wrote: gcc/ * gcov-io.cc (GCOV_MODE_STDIN): Define. (gcov_position): For gcov-tool, return calculated position if file is stdin. (gcov_open): For gcov-tool, use stdin if filename is NULL. (gcov_close): For gcov-tool, do n

[PATCH] tree-optimization/105185 - simplify modref query in SCCVN

This simplifies the modref query for calls in SCCVN again after r12-8019-g4be08315124281, avoiding an ICE when the modref analyzed access lacks an actual argument on the caller side. It effectively reverts r12-7531-gdc46350d44c294. Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed. 2022

Re: [PING^1][PATCH] postscan_insn hook not called after input_asm

Hi, I would like to draw your attention on this patch, it's a pretty tiny patch which does not affect many targets. - Original Message - From: "gcc-patches" To: "gcc-patches" Sent: Tuesday, March 29, 2022 4:10:16 PM Subject: [PATCH] postscan_insn hook not called after input_asm Hi, W