[vect-patterns] Refactor widen_plus/widen_minus as internal_fns

Hi all, This refactor allows widening vect patterns (such as widen_plus/widen_minus) to be represented as either internal_fns or tree_codes and replaces the current widen_plus/widen_minus with internal_fn versions. This refactor is split into 3 patches. Boostrapped and regression tested on aar

Re: [Patch] Fortran/openmp: Add support for 2 argument num_teams clause

On Thu, Nov 11, 2021 at 04:04:04PM +0100, Tobias Burnus wrote: > Just the Fortran FE work + Fortranized version for the C tests. > > Tobias > - > Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 > München; Gesellschaft mit beschränkter Haftung; Geschäf

Re: [PATCH v2] libgcc: fix backtrace fallback on PowerPC Big-endian. [PR103004]

Hi! On Thu, Nov 11, 2021 at 11:40:10AM -0300, Raphael Moreira Zinsly wrote: > Changes since v1: > - Removed -Wmissing-prototypes fix. > - Fixed formatting of Changelog and patch. > > --->8--- > > At the end of the backtrace stream _Unwind_Find_FDE() may not be able > to find the fram

[PATCH] libbacktrace: fix UBSAN issues

Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin Fix issues mentioned in the PR. PR libbacktrace/103167 libbacktrace/ChangeLog: * elf.c (elf_uncompress_lzma_block): Cast to unsigned int. (elf_uncompress_lzma):

Re: [PATCH v1 8/8] RISC-V: bitmanip: relax minmax to operate on GPR

Hi Philipp: We can't pretend we have SImode min/max instruction without that semantic. Give this testcase, x86 and rv64gc print out 8589934592 8589934591 = 0, but with this patch and compile with rv64gc_zba_zbb -O3, the output become 8589934592 8589934591 = 8589934592 -Testcase---

Re: [PATCH 1v2/3][vect] Add main vectorized loop unrolling

Hi, This is the rebased and reworked version of the unroll patch.  I wasn't entirely sure whether I should compare the costs of the unrolled loop_vinfo with the original loop_vinfo it was unrolled of. I did now, but I wasn't too sure whether it was a good idea to... Any thoughts on this? Re

Re: [PATCH v1 8/8] RISC-V: bitmanip: relax minmax to operate on GPR

Kito, Unless I am missing something, the problem is not the relaxation to GPR, but rather the sign-extending pattern I had squashed into the same patch. If you disable "si3_sext", a sext.w will be have to be emitted after the 'max' and before the return (or before the SImode output is consumed as

Re: [PATCH v1 8/8] RISC-V: bitmanip: relax minmax to operate on GPR

IIRC it's not work even without sign extend pattern since I did similar experimental before (not for RISC-V, but same concept), I guess I need more time to test that. Philipp Tomsich 於 2021年11月12日 週五 00:18 寫道： > Kito, > > Unless I am missing something, the problem is not the relaxation to > GPR,

[PATCH] fixincludes: fix portability issues about getcwd() [PR21283, PR80047]

[Revised to handle PR 21283.] POSIX says: On some implementations, if buf is a null pointer, getcwd() may obtain size bytes of memory using malloc(). In this case, the pointer returned by getcwd() may be used as the argument in a subsequent call to free(). Invoking getcwd() with b

Enable pure/const discovery in modref

Hi, this patch enables the pure/const discovery in modref, so we newly can handle some extra cases, for example: struct a {int a,b,c;}; __attribute__ ((noinline)) int init (struct a *a) { a->a=1; a->b=2; a->c=3; } int const_fn () { struct a a; init (&a); return a.a + a.b + a.c; } Her

[PATCH] Implement -fprofile-prefix-map.

It's functionality that is analogous to -ffile-prefix-map, this time for gcov purpose. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin PR gcov-profile/96092 gcc/ChangeLog: * common.opt: New option. * coverage

Re: [PATCH] fixincludes: don't assume getcwd() can handle NULL argument

On 11/11/2021 6:04 AM, Eric Gallager via Gcc-patches wrote: On Tue, Nov 9, 2021 at 8:50 AM Xi Ruoyao via Gcc-patches wrote: POSIX says: On some implementations, if buf is a null pointer, getcwd() may obtain size bytes of memory using malloc(). In this case, the pointer returned

Re: [PATCH][V2] rs6000: Remove unnecessary option manipulation.

PING^1 On 11/4/21 13:36, Martin Liška wrote: Sending the patch in a separate thread. Ready for master? Cheers, Martin gcc/ChangeLog: * config/rs6000/rs6000.c (rs6000_override_options_after_change): Do not set flag_rename_registers, it's already enabled with EnabledBy(funroll

Re: [PATCH v1 8/8] RISC-V: bitmanip: relax minmax to operate on GPR

Hi Philipp: This testcase got wrong result with this patch even w/o si3_sext pattern: #include #define MAX(A, B) ((A) > (B) ? (A) : (B)) long long __attribute__((noinline, noipa)) foo6(long long a, long long b, int c) { int xa = a; int xb = b; return MAX(MAX(xa, xb), c); } int main() {

Re: [PATCH] tree-optimization/103188 - avoid running ranger on not-up-to-date SSA

Thanks for doing this! > > + gimple_ranger *ranger = new gimple_ranger; > + path_range_query *query = new path_range_query (*ranger, /*resolve=*/true); Hmmm, it looks like both clients are now instantiating a gimple_ranger just so they can pass it down to the path_range_query. Maybe we should

Re: [PATCH] rs6000: Fix a handful of 32-bit built-in function problems in the new support

Hi! On 11/11/21 7:11 AM, Segher Boessenkool wrote: > On Wed, Nov 10, 2021 at 03:28:18PM -0600, Bill Schmidt wrote: >> On 11/10/21 2:33 AM, Segher Boessenkool wrote: >>> On Tue, Nov 09, 2021 at 03:46:54PM -0600, Bill Schmidt wrote: * config/rs6000/rs6000-builtin-new.def (CMPB): Flag as no32

Re: [PATCH] tree-optimization/103188 - avoid running ranger on not-up-to-date SSA

On November 11, 2021 5:43:48 PM GMT+01:00, Aldy Hernandez wrote: >Thanks for doing this! > >> >> + gimple_ranger *ranger = new gimple_ranger; >> + path_range_query *query = new path_range_query (*ranger, >> /*resolve=*/true); > >Hmmm, it looks like both clients are now instantiating a gimple_r

Re: [PATCH] tree-optimization/103188 - avoid running ranger on not-up-to-date SSA

Like this. It simplifies both loop-ch and the threader. I'll push this pending tests unless someone objects. On Thu, Nov 11, 2021 at 5:43 PM Aldy Hernandez wrote: > > Thanks for doing this! > > > > > + gimple_ranger *ranger = new gimple_ranger; > > + path_range_query *query = new path_range_q

[Patch] Fortran/openmp: Fix '!$omp end'

Found this when looking at the num_teams patch – and when converting clauses-1.c to clauses-1.f90. OK? Tobias - Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank T

[committed] diagnostic: fix unused variable 'def_tabstop' [PR103129]

Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Pushed to trunk as r12-5176-gabdff441a07f55d16e3d0e5ced3123c83d210a0a. gcc/ChangeLog: PR other/103129 * diagnostic-show-locus.c (def_policy): Use def_tabstop. Signed-off-by: David Malcolm --- gcc/diagnostic-show-locu

[PATCH] Remove loop crossing restriction from the backward threader.

We have much more thorough restrictions, that are shared between both threader implementations, in the registry. I've been meaning to remove the backward threader one, since it's only purpose was reducing the search space. Previously there was a small time penalty for its removal, but with the va

[PATCH] Make ranger optional in path_range_query.

All users of path_range_query are currently allocating a gimple_ranger only to pass it to the query object. It's tidier to just do it from path_range_query if no ranger was passed. Will push pending tests on x86-64 Linux. gcc/ChangeLog: * gimple-range-path.cc (path_range_query::path_ran

Re: [PATCH] Remove loop crossing restriction from the backward threader.

On 11/11/2021 10:24 AM, Aldy Hernandez wrote: We have much more thorough restrictions, that are shared between both threader implementations, in the registry. I've been meaning to remove the backward threader one, since it's only purpose was reducing the search space. Previously there was a

[AArch64] Enable generation of FRINTNZ instructions

Hi, This patch introduces two IFN's FTRUNC32 and FTRUNC64, the corresponding optabs and mappings. It also creates a backend pattern to implement them for aarch64 and a match.pd pattern to idiom recognize these. These IFN's (and optabs) represent a truncation towards zero, as if performed by fi

Re: [PATCH][V2] rs6000: Remove unnecessary option manipulation.

Hi! On Thu, Nov 04, 2021 at 01:36:06PM +0100, Martin Liška wrote: > Sending the patch in a separate thread. You forgot to send the commit message though? > * config/rs6000/rs6000.c (rs6000_override_options_after_change): > Do not set flag_rename_registers, it's already enabled with >

Re: [PATCH] vect: Remove vec_outside/inside_cost fields

> > Now afunc writes to __var_5_mma only indirectly so I think it is correct > > that > > we optimize the conditional out. > > > > Easy fix would be to add -fno-ipa-modref, but perhaps someone with > > better understanding of Fortran would help me to improve the testcase so > > the calls to matmul

Re: [Patch] Fortran/openmp: Fix '!$omp end'

On Thu, Nov 11, 2021 at 06:11:23PM +0100, Tobias Burnus wrote: > --- a/gcc/fortran/parse.c > +++ b/gcc/fortran/parse.c > @@ -915,15 +915,16 @@ decode_omp_directive (void) >matcho ("error", gfc_match_omp_error, ST_OMP_ERROR); >matcho ("end atomic", gfc_match_omp_eos_error, ST_OMP_END

Re: [PATCH] dwarf: Multi-register CFI address support.

On 09/11/2021 15:59, Jakub Jelinek wrote: > On Sun, Jun 13, 2021 at 02:27:38PM +0100, Hafiz Abid Qadeer wrote: >> *** with this patch (edited for brevity)*** >> >> 0024 CIE >> >> DW_CFA_def_cfa_expression: DW_OP_bregx SGPR49+0, DW_OP_const1u 0x20, >> DW_OP_shl, DW_OP_bregx

[PATCH v2] implement -Winfinite-recursion [PR88232]

On 11/10/21 2:27 PM, Marek Polacek wrote: On Tue, Nov 09, 2021 at 09:28:43PM -0700, Martin Sebor via Gcc-patches wrote: The attached patch adds support to the middle end for detecting infinitely recursive calls. The warning is controlled by the new -Winfinite-recursion option. The option name

Re: [PATCH v2] implement -Winfinite-recursion [PR88232]

On Thu, Nov 11, 2021 at 11:21:01AM -0700, Martin Sebor wrote: > On 11/10/21 2:27 PM, Marek Polacek wrote: > > On Tue, Nov 09, 2021 at 09:28:43PM -0700, Martin Sebor via Gcc-patches > > wrote: > > > The attached patch adds support to the middle end for detecting > > > infinitely recursive calls. T

Re: [PATCH v3 0/5] fortran: Ignore unused arguments for scalarisation [PR97896]

Hi Mikael, Regression-tested on x86_64-linux-gnu. Ok for master? This looks quite good, and is (I think) a cleaner version than what we had before. OK. Thanks a lot for the patch(es)! Best regards Thomas

Re: [PATCH v1 8/8] RISC-V: bitmanip: relax minmax to operate on GPR

Kito, Thanks for the reality-check: the subreg-expressions are getting in the way. I'll drop this from v2, as a permanent resolution for this will be a bit more involved. Philipp. On Thu, 11 Nov 2021 at 17:42, Kito Cheng wrote: > > Hi Philipp: > > This testcase got wrong result with this patch

Re: [PATCH 0/2] fortran: Ignore unused arguments for scalarisation [PR97896]

On 07.11.21 17:17, Mikael Morin via Fortran wrote: Regression-tested on x86_64-linux-gnu. Ok for master and 11 branch? OK. Just one remark: Since just reverting my old patch would introduce a regression for that one revision, please squash the patches before committing. Thanks a lot for th

[PATCH] openmp: Honor OpenMP 5.1 num_teams lower bound

Hi! The following patch implements what I've been talking about earlier, honor that for explicit num_teams clause we create at least the lower-bound (if not specified, upper-bound) teams in the league. For host fallback, it still means we only have one thread doing all the teams, sequentially one

[r12-5150 Regression] FAIL: gfortran.dg/vector_subscript_1.f90 -Os execution test on Linux/x86_64

On Linux/x86_64, 3e5a19053310ad090b930fbecebceb28bd1b91a4 is the first bad commit commit 3e5a19053310ad090b930fbecebceb28bd1b91a4 Author: Aldy Hernandez Date: Thu Nov 11 11:27:07 2021 +0100 Resolve entry loop condition for the edge remaining in the loop. caused FAIL: gfortran.dg/vector_s

Re: [PATCH] libbacktrace: fix UBSAN issues

On Thu, Nov 11, 2021 at 7:39 AM Martin Liška wrote: > > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. > > Ready to be installed? > Thanks, > Martin > > Fix issues mentioned in the PR. > > PR libbacktrace/103167 > > libbacktrace/ChangeLog: > > * elf.c (elf_u

Re: [r12-5150 Regression] FAIL: gfortran.dg/vector_subscript_1.f90 -Os execution test on Linux/x86_64

This is expected. It was failing at all optimization levels except -Os. The oversight has been fixed :-). On Thu, Nov 11, 2021, 20:14 sunil.k.pandey wrote: > On Linux/x86_64, > > 3e5a19053310ad090b930fbecebceb28bd1b91a4 is the first bad commit > commit 3e5a19053310ad090b930fbecebceb28bd1b91a4 >

[PATCH 0/3] gimple-fold improvements

This patchset improves folding in cases where input lengths and/or destination sizes may not be constant but are range bound. Tested on x86_64 with a full bootstrap build and verified that there are no regressions resulting from this patchset. Also tested a build of bash, which results in 3 __mem

[PATCH 1/3] gimple-fold: Transform stp*cpy_chk to str*cpy directly

Avoid going through another folding cycle and use the ignore flag to directly transform BUILT_IN_STPCPY_CHK to BUILT_IN_STRCPY when set, likewise for BUILT_IN_STPNCPY_CHK to BUILT_IN_STPNCPY. Dump the transformation in dump_file so that we can verify in tests that the direct transformation actuall

[PATCH 3/3] gimple-fold: Use ranges to simplify strncat and snprintf

Remove the warnings for strncat since it is already handled (and even the error messages look identical) in gimple-ssa-warn-access. Instead, use len range to determine if it is within bounds of source and destination and simplify it to strcat if it's safe. Likewise for snprintf, use ranges to det

[PATCH 2/3] gimple-fold: Use ranges to simplify _chk calls

Instead of comparing LEN and SIZE only if they are constants, use their ranges to decide if LEN will always be lower than or same as SIZE. This change ends up putting the stringop-overflow warning line number against the strcpy implementation, so adjust the warning check to be line number agnostic

[committed] libstdc++: Remove public std::vector::data() member

Tested x86_64-linux, pushed to trunk. This function only exists to avoid an error in the debug mode vector, so doesn't need to be public. libstdc++-v3/ChangeLog: * include/bits/stl_bvector.h (vector::data()): Give protected access, and delete for C++11 and later. --- libstdc++-

[committed] libstdc++: Make pmr::memory_resource::allocate implicitly create objects

Tested x86_64-linux, pushed to trunk. Calling the placement version of ::operator new "implicitly creates objects in the returned region of storage" as per [intro.object]. This allows the returned memory to be used as storage for implicit-lifetime types (including arrays) without additional actio

Re: [PATCH 16/18] rs6000: Test case adjustments

Hi Segher, [Sorry to be answering these out of order...] On 11/5/21 5:37 PM, Segher Boessenkool wrote: > On Wed, Sep 01, 2021 at 11:13:52AM -0500, Bill Schmidt wrote: >> * gcc.target/powerpc/bfp/scalar-extract-exp-2.c: Adjust. > My favourite changelog entry! But, adjust to what? This is th

Go patch committed: Traverse func subexprs when creating func descriptors

This patch to the Go frontend fixes the Create_func_descriptors pass to traverse the subexpressions of the function in a Call_expression. There are no subexpressions in the normal case of calling a function a method directly, but there are subexpressions when in code like F().M() when F returns an

Re: [PATH][_GLIBCXX_DEBUG] Fix unordered container merge

On Wed, 10 Nov 2021 at 11:55, Jonathan Wakely wrote: > > > On Tue, 9 Nov 2021 at 16:25, Jonathan Wakely wrote: > >> >> >> On Mon, 8 Nov 2021 at 21:36, François Dumont >> wrote: >> >>> Yet another version this time with only 1 guard implementation. The >>> predicate to invalidate the safe iterat

[PATCH, committed] rs6000: Fix test_mffsl.c to require Power9 support

Hi! Per previous discussion, committed the following as obvious. commit 8a8458ac6bbc4263dd2c1ee55979b29fc7195794 Author: Bill Schmidt Date: Thu Nov 11 14:36:04 2021 -0600 rs6000: Fix test_mffsl.c to require Power9 support 2021-11-11 Bill Schmidt gcc/testsuite/

Re: [PATCH 16/18] rs6000: Test case adjustments

On 11/11/21 2:06 PM, Bill Schmidt wrote: > >>> --- a/gcc/testsuite/gcc.target/powerpc/int_128bit-runnable.c >>> +++ b/gcc/testsuite/gcc.target/powerpc/int_128bit-runnable.c >>> @@ -11,9 +11,9 @@ >>> /* { dg-final { scan-assembler-times {\mvrlq\M} 2 } } */ >>> /* { dg-final { scan-assembler-times

Re: [PATH][_GLIBCXX_DEBUG] Fix unordered container merge

On 11/11/21 9:41 pm, Jonathan Wakely wrote: On Wed, 10 Nov 2021 at 11:55, Jonathan Wakely > wrote: On Tue, 9 Nov 2021 at 16:25, Jonathan Wakely mailto:jwak...@redhat.com>> wrote: On Mon, 8 Nov 2021 at 21:36, François Dumont mailto:frs.dum...

[PATCH v2] implement -Winfinite-recursion [PR88232]

Attached is a v2 of the solution I posted earlier this week with a few tweaks made after a more careful consideration of the problem and possible false negatives and positives. 1) It avoids warning for [apparently infinitely recursive] calls in noreturn functions where the recursion may be pre

Re: [PATH][_GLIBCXX_DEBUG] Fix unordered container merge

On Thu, 11 Nov 2021 at 21:33, François Dumont wrote: > On 11/11/21 9:41 pm, Jonathan Wakely wrote: > > > > On Wed, 10 Nov 2021 at 11:55, Jonathan Wakely wrote: > >> >> >> On Tue, 9 Nov 2021 at 16:25, Jonathan Wakely wrote: >> >>> >>> >>> On Mon, 8 Nov 2021 at 21:36, François Dumont >>> wrote:

Re: rs6000: Fix up flag_shrink_wrap handling in presence of -mrop-protect [PR101324]

Sorry for taking so long to get back to this. On 10/29/21 4:45 PM, Segher Boessenkool wrote: > On Wed, Oct 27, 2021 at 10:17:39PM -0500, Peter Bergner wrote: >> +/* Ensure hashst comes after mflr and hashchk comes after ld 0,16(1). */ >> +/* { dg-final { scan-assembler "mflr 0.*hashst 0," } } */

[PATCH] rs6000: testsuite: Add rop_ok effective-target function

This patch adds a new effective-target function that tests whether it is safe to emit the ROP-protect instructions and updates the ROP test cases to use it. Segher, as we discussed offline, this uses the double [] which you said isn't needed in general regex's, but for some reason is needed in the

[PATCH][GCC] aarch64: Add LS64 extension and intrinsics

Hi, This patch is adding support for LS64 (Armv8.7-A Load/Store 64 Byte extension) which is part of Armv8.7-A architecture. Changes include missing plumbing for TARGET_LS64, LS64 data structure and intrinsics defined in ACLE [0]. Machine description of intrinsics is using new V8DI mode added in a

Re: [PATCH] testsuite/102690 - XFAIL g++.dg/warn/Warray-bounds-16.C

On 11/11/21 1:18 AM, Richard Biener wrote: On Wed, 10 Nov 2021, Martin Sebor wrote: On 11/10/21 3:09 AM, Richard Biener via Gcc-patches wrote: This XFAILs the bogus diagnostic test and rectifies the expectation on the optimization. Tested on x86_64-unknown-linux-gnu, pushed. 2021-11-10 Rich

[PATCH] c++: implicit dummy object in requires clause [PR103198]

In the testcase below satisfaction misbehaves for f and g ultimately because find_template_parameters fails to notice that the constraint 'val.x' depends on the template parameters of the class template. In contrast, satisfaction works just fine for h. The problem seems to come down to a differenc

Re: [PATCH] testsuite/102690 - XFAIL g++.dg/warn/Warray-bounds-16.C

On Thu, 11 Nov 2021, Martin Sebor wrote: > On 11/11/21 1:18 AM, Richard Biener wrote: > > On Wed, 10 Nov 2021, Martin Sebor wrote: > > > >> On 11/10/21 3:09 AM, Richard Biener via Gcc-patches wrote: > >>> This XFAILs the bogus diagnostic test and rectifies the expectation > >>> on the optimizatio

RE: [PATCH] middle-end: fix de-optimizations with bitclear patterns on signed values

> -Original Message- > From: Jakub Jelinek > Sent: Thursday, November 4, 2021 4:11 PM > To: Tamar Christina > Cc: Jonathan Wakely ; Richard Biener > ; gcc-patches@gcc.gnu.org; nd > Subject: Re: [PATCH] middle-end: fix de-optimizations with bitclear patterns > on signed values > > On T

<    1   2