[PATCH] ppc: testsuite: vec-mul requires vsx runtime

vec-mul is an execution test, but it only requires a powerpc_vsx_ok effective target, which is enough only for compile tests. In order to To check for runtime and execution environment support, we need to require vsx_hw. Make that a condition for execution, but still perform a compile test if

[PATCH] [PR105324] libstdc++: testsuite: pr105324 requires FP from_char

The floating-point overloads of from_char are only declared if _GLIBCXX_HAVE_USELOCALE is #defined as nonzero. That's exposed from charconv as _cpp_lib_to_chars >= 201611L, so guard the test body with that. Regstrapped on ppc64le-linux-gnu, and tested on x86_64-linux-gnu-x-ppc{,64}-vx7r2

Re: [PATCH] testsuite: vect: update unaligned message

On Apr 28, 2022, Richard Biener wrote: > On Thu, 28 Apr 2022, Alexandre Oliva wrote: >> >> gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c covers ppc variants >> that accept and reject misaligned accesses. The message that it >> expects for rejection was removed in the gcc-11 development cycle

[PATCH v2] libstdc++: ppc: conditionalize vsx-only simd intrinsics

On May 2, 2022, Segher Boessenkool wrote: > Send full patches always please. I'll try to remember that. In case I fail, I hope you won't mind too much reminding me. (You'd also asked me not to send patches as followups, but... revised versions of a patch still belong in the same thread,

Ping #5: [PATCH, V4] Eliminate power8 fusion options, use power8 tuning, PR target/102059

Ping #5: | Date: Tue, 12 Apr 2022 21:14:55 -0400 | From: Michael Meissner | Subject: [PATCH, V4] Eliminate power8 fusion options, use power8 tuning, PR target/102059 | Message-ID: https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593153.html We really need closure on this so I can do the

[pushed] c++: improve template-id location

On PR102629 I noticed that we were giving the entire lambda as the location for this template-id. Tested x86_64-pc-linux-gnu, applying to trunk. gcc/cp/ChangeLog: * pt.cc (tsubst_copy_and_build) [TEMPLATE_ID_EXPR]: Copy location. (do_auto_deduction): Use expr location.

Re: [PATCH] libstdc++: ppc: conditionalize vsx-only simd intrinsics

Hi! On Thu, Apr 28, 2022 at 10:53:40PM -0300, Alexandre Oliva wrote: > On Apr 28, 2022, Segher Boessenkool wrote: > > On Thu, Apr 28, 2022 at 03:09:54AM -0300, Alexandre Oliva wrote: > >> +"no __intrinsic_type support for [long] double on PPC w/o > >> VSX"); > > This change isn't in

[pushed] c++: also note name used in enclosing class

While looking at PR96645 I noticed that while we were diagnosing names changing meaning in the full class context, we weren't doing this for lookups in nested class bodies. Note that this breaks current range-v3; I've submitted a pull request to fix its violation of the rule. Tested

Re: [PATCH] ipa-visibility: Optimize TLS access [PR99619]

On 5/2/22 18:04, Martin Jambor wrote: > (Minor nit and I don't care too much, but in GCC we traditionally > specify co-authors in the ChangeLog entry beginning by providing more > names, one per line. But perhaps we want to adapt more widely used > practices.) Hello. Using Co-Authored-By is

[PATCH] c++: partial spec constraint checking context [PR105220]

Currently when checking the constraints of a class template, we do so in the context of the template, not the specialized type. This is the best we can do for a primary template since the specialized type is valid only if the primary template's constraints are satisfied. But for a partial

Re: [PATCH] x86: Add missing .note.GNU-stack to assembly source

On Fri, Apr 29, 2022 at 10:38 AM H.J. Lu wrote: > > Add .note.GNU-stack assembly source to avoid linker warning: > > ld: warning: /tmp/ccPZSZ7Z.o: missing .note.GNU-stack section implies > executable stack > ld: NOTE: This behaviour is deprecated and will be removed in a future > version of the

[ping2][PATCH 0/8][RFC] Support BTF decl_tag and type_tag annotations

Pinging this series again. Link: https://gcc.gnu.org/pipermail/gcc-patches/2022-April/592685.html This series adds new C-family frontend attributes for recording string "tags" in DWARF and BTF debug info to support kernel use cases. There remains one issue in the implementation which has not

Re: [PATCH] ipa-visibility: Optimize TLS access [PR99619]

On Mon, 2 May 2022, Martin Jambor wrote: > > Co-Authored-By: Alexander Monakov > > (Minor nit and I don't care too much, but in GCC we traditionally > specify co-authors in the ChangeLog entry beginning by providing more > names, one per line. But perhaps we want to adapt more widely used >

[PATCH] c++: parse error with >= in template argument list [PR105436]

This patch fixes an oversight whereby we treated >= as the end of a template argument. This causes problems in C++14, because in cp_parser_template_argument we go different ways for C++14 and C++17: /* It must be a non-type argument. In C++17 any constant-expression is allowed. */ if

[PATCH] c++: wrong parse with functors [PR64679]

Consider struct F { F(int) {} F operator()(int) const { return *this; } }; and F(i)(0)(0); where we're supposed to first call the constructor and then invoke the operator() twice. However, we parse this as an init-declarator: "(i)" looks like a perfectly valid declarator, then

Re: [PATCH] ipa-visibility: Optimize TLS access [PR99619]

Hello, On Sun, Apr 17 2022, Artem Klimov via Gcc-patches wrote: > Fix issue PR99619, which asks to optimize TLS access based on > visibility. The fix is implemented as an IPA optimization, which allows > to take optimized visibility status into account (as well as avoid > modifying all language

Make 'c-c++-common/goacc/kernels-decompose-pr100400-1-*.c' behave consistently, regardless of checking level (was: GCC 12.1 Release Candidate available from gcc.gnu.org)

Hi! On 2022-05-01T11:02:29+0100, Iain Sandoe via Gcc wrote: >> On 29 Apr 2022, at 15:34, Jakub Jelinek via Gcc wrote: >> >> The first release candidate for GCC 12.1 is available from >> >> https://gcc.gnu.org/pub/gcc/snapshots/12.1.0-RC-20220429/ >>

[PATCH] Assume a call is expensive when it mismatches

This makes sure to not consider calls to builtin decls with mismatching arguments as inexpensive. Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed. 2022-04-13 Richard Biener * tree-scalar-evolution.cc (expression_expensive_p): Never consider mismatched calls as

Re: [PATCH] PR tree-optimization/102950: Improved EVRP for signed BIT_XOR_EXPR.

On Tue, Feb 1, 2022 at 9:57 AM Roger Sayle wrote: > > > This patch fixes PR tree-optimization/102950, which is a P2 regression, > by providing better range bounds for BIT_XOR_EXPR, BIT_AND_EXPR and > BIT_IOR_EXPR on signed integer types. In general terms, any binary > bitwise operation on

Re: [PATCH] PR middle-end/98865: Optimize (a>>63)*b as -(a>>63) in match.pd.

On Wed, Apr 20, 2022 at 8:35 PM Roger Sayle wrote: > > > This patch implements the constant folding optimization(s) described in > PR middle-end/98865, which should help address the serious performance > regression of Botan AES-128/XTS mentioned in PR tree-optimization/98856. > This combines

[PATCH] tree-optimization/104240 - SLP discovery with swapped comparisons

The following extends SLP discovery to handle swapped operands in comparisons. Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed. 2022-05-02 Richard Biener PR tree-optimization/104240 * tree-vect-slp.cc (op1_op0_map): New. (vect_get_operand_map): Handle

[PATCH] c++: Don't emit deprecated warnings or unavailable errors on lambda declarations

Hi! On the following testcase, we emit deprecated warnings or unavailable errors even on merge declarations of those lambdas (the dg-bogus directives), while IMHO we should emit them only when something actually calls those lambdas. The following patch temporarily disables that diagnostics

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On 5/2/22 11:36, Richard Biener wrote: > Linkers will need heuristics anyway for older plugins and I think > LLVM could just behave here. Leaving that for the future, I may return to it. Right now, the benefit is pretty low to me. Martin

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On Mon, May 2, 2022 at 11:36 AM Richard Biener wrote: > > On Mon, May 2, 2022 at 11:27 AM Martin Liška wrote: > > > > On 5/2/22 11:14, Richard Biener wrote: > > > On Mon, May 2, 2022 at 11:08 AM Martin Liška wrote: > > >> > > >> On 5/2/22 11:03, Richard Biener wrote: > > >>> In fact I think GCC

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On Mon, May 2, 2022 at 11:27 AM Martin Liška wrote: > > On 5/2/22 11:14, Richard Biener wrote: > > On Mon, May 2, 2022 at 11:08 AM Martin Liška wrote: > >> > >> On 5/2/22 11:03, Richard Biener wrote: > >>> In fact I think GCC is correct in its handling and LLVM would need to dup > >>> () the >

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On 5/2/22 11:14, Richard Biener wrote: > On Mon, May 2, 2022 at 11:08 AM Martin Liška wrote: >> >> On 5/2/22 11:03, Richard Biener wrote: >>> In fact I think GCC is correct in its handling and LLVM would need to dup >>> () the >>> file descriptor. Was this issue raised with the LLVM folks? >>

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On Mon, May 2, 2022 at 11:08 AM Martin Liška wrote: > > On 5/2/22 11:03, Richard Biener wrote: > > In fact I think GCC is correct in its handling and LLVM would need to dup > > () the > > file descriptor. Was this issue raised with the LLVM folks? > > I don't know here. > > > I suspect the BFD

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On Mon, May 2, 2022 at 11:06 AM Jan Hubicka wrote: > > > On Mon, May 2, 2022 at 10:51 AM Richard Biener > > wrote: > > > > > > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote: > > > > > > > > On 5/2/22 10:09, Richard Biener wrote: > > > > > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote:

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On 5/2/22 11:03, Richard Biener wrote: > In fact I think GCC is correct in its handling and LLVM would need to dup () > the > file descriptor. Was this issue raised with the LLVM folks? I don't know here. > I suspect the BFD > linker will also not work with LLVM due to this? I'm not sure BFD

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

> On Mon, May 2, 2022 at 10:51 AM Richard Biener > wrote: > > > > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote: > > > > > > On 5/2/22 10:09, Richard Biener wrote: > > > > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote: > > > >> > > > >> Hi. > > > >> > > > >> This in a new plug-in

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On 5/2/22 11:00, Richard Biener wrote: > On Mon, May 2, 2022 at 10:57 AM Martin Liška wrote: >> >> On 5/2/22 10:51, Richard Biener wrote: >>> On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote: On 5/2/22 10:09, Richard Biener wrote: > On Mon, May 2, 2022 at 9:52 AM Martin Liška

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On Mon, May 2, 2022 at 11:00 AM Richard Biener wrote: > > On Mon, May 2, 2022 at 10:57 AM Martin Liška wrote: > > > > On 5/2/22 10:51, Richard Biener wrote: > > > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote: > > >> > > >> On 5/2/22 10:09, Richard Biener wrote: > > >>> On Mon, May 2, 2022

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On Mon, May 2, 2022 at 10:57 AM Martin Liška wrote: > > On 5/2/22 10:51, Richard Biener wrote: > > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote: > >> > >> On 5/2/22 10:09, Richard Biener wrote: > >>> On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote: > > Hi. > > This

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On Mon, May 2, 2022 at 10:54 AM Richard Biener wrote: > > On Mon, May 2, 2022 at 10:51 AM Richard Biener > wrote: > > > > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote: > > > > > > On 5/2/22 10:09, Richard Biener wrote: > > > > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote: > > > >> >

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On 5/2/22 10:51, Richard Biener wrote: > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote: >> >> On 5/2/22 10:09, Richard Biener wrote: >>> On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote: Hi. This in a new plug-in function that helps identifying compiler by a

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On Mon, May 2, 2022 at 10:51 AM Richard Biener wrote: > > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote: > > > > On 5/2/22 10:09, Richard Biener wrote: > > > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote: > > >> > > >> Hi. > > >> > > >> This in a new plug-in function that helps

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote: > > On 5/2/22 10:09, Richard Biener wrote: > > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote: > >> > >> Hi. > >> > >> This in a new plug-in function that helps identifying compiler > >> by a linker. Will be used in mold linker. > >> > >>

Re: [PATCH] ipa-visibility: Optimize TLS access [PR99619]

Hi, I'd like to ping this patch on behalf of Artem. Alexander On Sun, 17 Apr 2022, Artem Klimov wrote: > Fix issue PR99619, which asks to optimize TLS access based on > visibility. The fix is implemented as an IPA optimization, which allows > to take optimized visibility status into account

Re: [PATCH] gcov: Fix first time gcov info dump

On 5/2/22 10:43, Sebastian Huber wrote: > This patch fixes an issue introduced by commit > ef9a53feae5701953da9161afef2aea0329ec8b2: Works for me, please install it. Martin > > gcc --coverage main.c && ./a.out > libgcov profiling error:a-main.gcda:Error writing > > gcc/ChangeLog: > > *

[PATCH] tree-optimization/105437 - BB vect with extern defs of throwing stmts

We have to watch out for vectorized stmt insert locations if the def from the last stmt alters control flow. We constrain region building so we know the def is outside of the current region and thus we can insert at the region start point. Bootstrapped and tested on x86_64-unknown-linux-gnu,

[PATCH] gcov: Fix first time gcov info dump

This patch fixes an issue introduced by commit ef9a53feae5701953da9161afef2aea0329ec8b2: gcc --coverage main.c && ./a.out libgcov profiling error:a-main.gcda:Error writing gcc/ChangeLog: * gcov-io.cc (gcov_rewrite): Clear the file error status. --- gcc/gcov-io.cc | 5 - 1 file

Re: [PATCH] alias: Fix -fcompare-debug issues caused by compare_base_symbol_refs [PR105415]

On Mon, 2 May 2022, Jakub Jelinek wrote: > On Fri, Apr 29, 2022 at 01:23:46PM +0200, Richard Biener wrote: > > On Fri, 29 Apr 2022, Jakub Jelinek wrote: > > > > > On Fri, Apr 29, 2022 at 01:11:31PM +0200, Jakub Jelinek via Gcc-patches > > > wrote: > > > > Depends. DECL_IN_CONSTANT_POOL decls

Re: [PATCH] alias: Fix -fcompare-debug issues caused by compare_base_symbol_refs [PR105415]

On Fri, Apr 29, 2022 at 01:23:46PM +0200, Richard Biener wrote: > On Fri, 29 Apr 2022, Jakub Jelinek wrote: > > > On Fri, Apr 29, 2022 at 01:11:31PM +0200, Jakub Jelinek via Gcc-patches > > wrote: > > > Depends. DECL_IN_CONSTANT_POOL decls can appear 2 ways, through > > >

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On 5/2/22 10:09, Richard Biener wrote: > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote: >> >> Hi. >> >> This in a new plug-in function that helps identifying compiler >> by a linker. Will be used in mold linker. >> >> Patch can bootstrap on x86_64-linux-gnu and survives regression tests. >>

Re: [PATCH] LTO plugin: add ld_plugin_version callback.

On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote: > > Hi. > > This in a new plug-in function that helps identifying compiler > by a linker. Will be used in mold linker. > > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. > > Ready to be installed? It looks a bit backward

Re: [PATCH] i386: simplify cpu_feature handling

On 3/31/22 09:01, Martin Liška wrote: > @Jakub: May I install it once stage1 opens? May I please ping this? Thanks, Martin > > Cheers, > Martin > > On 1/3/22 12:43, Martin Liška wrote: >> PING: Jakub? >> >> On 12/15/21 10:57, Martin Liška wrote: >>> On 12/14/21 17:12, Jakub Jelinek wrote:

[PATCH] LTO plugin: add ld_plugin_version callback.

Hi. This in a new plug-in function that helps identifying compiler by a linker. Will be used in mold linker. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin include/ChangeLog: * plugin-api.h (enum ld_plugin_compiler): New

[PATCH] Support LDPT_GET_SYMBOLS_V3.

That supports skipping of an object file (LDPS_NO_SYMS). The API will be used by mold and is there for some time in linkers. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin lto-plugin/ChangeLog: * lto-plugin.c (struct

Re: [PATCH] Replace EVRP in DOM with ranger.

On Mon, May 2, 2022 at 8:30 AM Richard Biener wrote: > > On Fri, Apr 29, 2022 at 6:22 PM Aldy Hernandez wrote: > > > > On Fri, Apr 29, 2022 at 12:13 PM Richard Biener > > wrote: > > > > > > On Fri, Apr 29, 2022 at 11:53 AM Aldy Hernandez wrote: > > > > > > > > On Fri, Apr 29, 2022 at 9:09 AM

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

On Tue, Apr 26, 2022 at 04:40:33PM +0200, Hans-Peter Nilsson wrote: > > From: Thomas Koenig via Gcc-patches > > Date: Fri, 22 Apr 2022 15:59:45 +0200 > > > Hi Mikael, > > > > > Ping for the four patches starting at > > > https://gcc.gnu.org/pipermail/fortran/2022-April/057759.html : > > >

Re: [COMMITTED] Denormalize VR_VARYING to VR_RANGE before passing it to set_range_info_raw.

On Mon, May 2, 2022 at 8:34 AM Richard Biener wrote: > > On Sun, May 1, 2022 at 2:15 PM Aldy Hernandez via Gcc-patches > wrote: > > > > We are ICEing in set_range_info_raw because value_range_kind cannot be > > VR_VARYING, since SSA_NAME_RANGE_TYPE can only hold VR_RANGE / > > VR_ANTI_RANGE.

Re: [COMMITTED] Denormalize VR_VARYING to VR_RANGE before passing it to set_range_info_raw.

On Sun, May 1, 2022 at 2:15 PM Aldy Hernandez via Gcc-patches wrote: > > We are ICEing in set_range_info_raw because value_range_kind cannot be > VR_VARYING, since SSA_NAME_RANGE_TYPE can only hold VR_RANGE / > VR_ANTI_RANGE. Most of the time setting a VR_VARYING as a global > range makes no

Re: [gcov v2 11/14] gcov: Record EOF error during read

> @@ -385,7 +395,11 @@ gcov_read_bytes (void *buffer, unsigned count) > >unsigned read = fread (buffer, count, 1, gcov_var.file); >if (read != 1) > -return NULL; > +{ > + if (feof (gcov_var.file)) > + gcov_var.error = GCOV_FILE_EOF; > + return NULL; > +} Hello.

Re: [patch, fortran, doc] Mention new CONVERT options for POWER

On Sat, Apr 30, 2022 at 1:26 AM Bernhard Reutner-Fischer wrote: > > On Fri, 29 Apr 2022 20:03:55 +0200 > Thomas Koenig wrote: > > > On 28.04.22 19:17, Bernhard Reutner-Fischer wrote: > > > ISTM that this should be s/mod.e/mode./ ? > > > > Yep, fixed as obvious and simple on trunk with > >

Re: [PATCH] Replace EVRP in DOM with ranger.

On Fri, Apr 29, 2022 at 6:22 PM Aldy Hernandez wrote: > > On Fri, Apr 29, 2022 at 12:13 PM Richard Biener > wrote: > > > > On Fri, Apr 29, 2022 at 11:53 AM Aldy Hernandez wrote: > > > > > > On Fri, Apr 29, 2022 at 9:09 AM Richard Biener > > > wrote: > > > > > > > > On Thu, Apr 28, 2022 at 8:44