[ping] Small adjustments to Aarch64 and i386 back-ends

For the Aarch64 back-end: https://gcc.gnu.org/pipermail/gcc-patches/2021-October/580952.html For the i386 back-end: https://gcc.gnu.org/pipermail/gcc-patches/2021-October/580992.html Thanks in advance. -- Eric Botcazou

Re: [PATCH] libsanitizer: Disable libbacktrace on sanitizer_platform_limits_freebsd.cpp

On Thu, 4 Nov 2021, H.J. Lu wrote: >> Ok. But please after committing mention the revision in >> libsanitizer/LOCAL_PATCHES. > include and libsanitizer should use 2 separate patches. The > libsanitizer patch should be in libsanitizer/LOCAL_PATCHES. Okay, thanks. This is the first part I

Re: [PATCH 0/4] config: Allow a host to opt out of PCH.

> On 8 Nov 2021, at 07:16, Richard Biener wrote: > > On Fri, Nov 5, 2021 at 5:37 PM Iain Sandoe wrote: >> >> >> >>> On 5 Nov 2021, at 15:25, Jakub Jelinek wrote: >>> >>> On Fri, Nov 05, 2021 at 11:31:58AM +0100, Richard Biener wrote: On Fri, Nov 5, 2021 at 10:54 AM Jakub Jelinek

Re: [PATCH 0/4] config: Allow a host to opt out of PCH.

On Fri, Nov 5, 2021 at 5:37 PM Iain Sandoe wrote: > > > > > On 5 Nov 2021, at 15:25, Jakub Jelinek wrote: > > > > On Fri, Nov 05, 2021 at 11:31:58AM +0100, Richard Biener wrote: > >> On Fri, Nov 5, 2021 at 10:54 AM Jakub Jelinek wrote: > >>> > >>> On Fri, Nov 05, 2021 at 10:42:05AM +0100,

Improve optimization of some builtins

Hi, for nested functions we output call to builtin_dwarf_cfa which initializes frame entry used only for debugging. This however prevents us from detecting functions containing nested functions as const/pure or analyze side effects in modref. builtin_dwarf_cfa is not documented and I wonder if

Re: [PATCH v3 1/4] Fix loop split incorrect count and probability

On 2021/10/27 15:44, Jan Hubicka wrote: >> On Wed, 27 Oct 2021, Jan Hubicka wrote: >> gcc/ChangeLog: * tree-ssa-loop-split.c (split_loop): Fix incorrect probability. (do_split_loop_on_cond): Likewise. --- gcc/tree-ssa-loop-split.c | 25

Re: [PATCH] PR middle-end/103059: reload: Also accept ASHIFT with indexed addressing

On Sun, 7 Nov 2021, Maciej W. Rozycki wrote: > On Fri, 5 Nov 2021, Hans-Peter Nilsson wrote: > > > > I was trying to chase another target I could use to regression-test this > > > with that does do scaled indexed addressing while still using old reload. > > > The i386 port would be a good

[PING] [PATCH v2] tree-optimization/101186 - extend FRE with "equivalence map" for condition prediction

Hi, Gentle ping on this. Di Zhao -Original Message- From: Di Zhao OS Sent: Monday, October 25, 2021 3:03 AM To: Richard Biener Cc: gcc-patches@gcc.gnu.org Subject: RE: [PATCH v2] tree-optimization/101186 - extend FRE with "equivalence map" for condition prediction Hi, Attached is a

Re: [PATCH v1 1/7] LoongArch Port: gcc

This patch does not arrive at  mail list. Send as an attachment in a compressed format. v1-0001-LoongArch-Port-gcc.patch.tar.xz Description: application/xz

Re: [PATCH] i386: Optimization for mm512_set1_pch.

On Fri, Nov 5, 2021 at 3:20 PM Kong, Lingling via Gcc-patches wrote: > > Hi, > > This patch is to support fold _mm512_fmadd_pch (a, _mm512_set1_pch(*(b)), c) > to 1 instruction vfmaddcph (%rsp){1to16}, %zmm1, %zmm2. > OK for master? > LGTM. > gcc/ChangeLog: > > * config/i386/sse.md

Re: [PATCH] i386: Support complex fma/conj_fma for _Float16.

On Fri, Nov 5, 2021 at 3:09 PM Kong, Lingling via Gcc-patches wrote: > > Hi, > > This patch is to support cmla_optab, cmul_optab, cmla_conj_optab, > cmul_conj_optab for vector _Float16. > Ok for master? LGTM. > gcc/ChangeLog: > > * config/i386/sse.md (cmul3): add new define_expand. >

Re: [PATCH 1/2] [Gimple] Simplify (trunc)fmax/fmin((extend)a, (extend)b) to MAX/MIN(a,b)

On Fri, Nov 5, 2021 at 5:52 PM Richard Biener wrote: > > On Fri, Nov 5, 2021 at 6:38 AM liuhongt wrote: > > > > a and b are same type as trunc type and has less precision than > > extend type, the transformation is guarded by flag_finite_math_only. > > > > Bootstrapped and regtested under

Re: [PATCH] c++: Implement -Wuninitialized for mem-initializers (redux) [PR19808]

On 11/5/21 5:22 PM, Marek Polacek via Gcc-patches wrote: 2021 update: Last year I posted a version of this patch: but it didn't make it in. The main objection seemed to be that the patch tried to do too much, and overlapped

PING [PATCH] restore ancient -Waddress for weak symbols [PR33925]

Ping: https://gcc.gnu.org/pipermail/gcc-patches/2021-October/582415.html On 10/23/21 5:06 PM, Martin Sebor wrote: On 10/4/21 3:37 PM, Jason Merrill wrote: On 10/4/21 14:42, Martin Sebor wrote: While resolving the recent -Waddress enhancement request (PR PR102103) I came across a 2007 problem

Re: [PATCH] Objective-C: fix protocol list count type (pertinent to non-LP64)

> On Oct 25, 2021, at 5:43 AM, Iain Sandoe wrote: > > Did you test objective-c++ on Darwin? > > I see a lot of fails of the form: > Excess errors: > : error: initialization of a flexible array member [-Wpedantic] Looked into this. It’s happening because obj-c++.dg/dg.exp has: set

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

Hi Mikael, thanks for working on this! Am 07.11.21 um 17:17 schrieb Mikael Morin via Gcc-patches: Hello, I repost this patch series initially targetted at the 11 branch only [1], and that I now would like to commit to master as well before. The problematic case is intrinsic procedures where

Re: [PATCH] PR middle-end/103059: reload: Also accept ASHIFT with indexed addressing

On Wed, 3 Nov 2021, Maciej W. Rozycki wrote: > I have not yet tracked down which change after commit c605a8bf9270 made > regressions appear in the test suites, however clearly the commit wasn't > as complete a change as it should have been. I'll see if I can find it > and will mention it in

Re: [PATCH] PR middle-end/103059: reload: Also accept ASHIFT with indexed addressing

On Fri, 5 Nov 2021, Hans-Peter Nilsson wrote: > > I was trying to chase another target I could use to regression-test this > > with that does do scaled indexed addressing while still using old reload. > > The i386 port would be a good candidate, but it has switched to LRA long > > ago with no

Re: [PATCH 11/18] rs6000: Builtin expansion, part 6

Hi! On Sun, Nov 07, 2021 at 09:28:09AM -0600, Bill Schmidt wrote: > Thank you for all of the reviews!  I appreciate your hard work and thorough > study of the patches. > > I've updated these 6 patches and combined them into 1, pushed today.  There > are still a couple of cleanups I haven't

Re: [patch, fortran, wwwdocs] Fix name of argument to CO_REDUCE

Hi Thomas, Am 07.11.21 um 19:18 schrieb Thomas Koenig via Fortran: Hello world, the attached patches fix the name of the function argument to CO_REDUCE to conform to Fortran 2018 instead of the TR. This is a user-visible change, so I have put this both into changes.html and porting_to.html.

[patch, fortran, wwwdocs] Fix name of argument to CO_REDUCE

Hello world, the attached patches fix the name of the function argument to CO_REDUCE to conform to Fortran 2018 instead of the TR. This is a user-visible change, so I have put this both into changes.html and porting_to.html. Regression-tested. OK for trunk? Best regards Thomas

[COMMITTED] Remove VRP threader.

Now that things have stabilized, we can remove the old code. I have left the hybrid threader in tree-ssa-threadedge, even though the VRP threader was the only user, because we may need it as an interim step for DOM threading removal. Tested on x86-64 Linux. p.s. I tried testing on ppc64le

[r12-4976 Regression] FAIL: gfortran.dg/vector_subscript_1.f90 -O3 -g execution test on Linux/x86_64

On Linux/x86_64, 4898e958a92d45dbf23c0f28bc7552689ba16ecc is the first bad commit commit 4898e958a92d45dbf23c0f28bc7552689ba16ecc Author: Jan Hubicka Date: Sun Nov 7 09:35:16 2021 +0100 Implement intra-procedural dataflow in ipa-modref flags propagation. caused FAIL:

[PATCH v3 5/5] fortran: Identify arguments by their names

This provides a new function to get the name of a dummy argument, so that identifying an argument can be made using just its name instead of a mix of name matching (for keyword actual arguments) and argument counting (for other actual arguments). gcc/fortran/ChangeLog: * interface.c

[PATCH 2/2] fortran: Ignore unused args in scalarization [PR97896]

The KIND argument of the INDEX intrinsic is a compile time constant that is used at compile time only to resolve to a kind-specific library function. That argument is otherwise completely ignored at runtime, and there is no code generated for it as the library procedure has no kind argument.

[PATCH 1/2] Revert "Remove KIND argument from INDEX so it does not mess up scalarization."

This reverts commit d09847357b965a2c2cda063827ce362d4c9c86f2 except for its testcase. gcc/fortran/ChangeLog: * intrinsic.c (add_sym_4ind): Remove. (add_functions): Use add_sym4 instead of add_sym4ind. Don’t special case the index intrinsic. * iresolve.c

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

Hello, I repost this patch series initially targetted at the 11 branch only [1], and that I now would like to commit to master as well before. The problematic case is intrinsic procedures where an argument is actually not used in the code generated (KIND argument of INDEX in the testcase), which

[PATCH v3 3/5] fortran: simplify elemental arguments walking

This adds two functions working with the wrapper struct gfc_dummy_arg and makes usage of them to simplify a bit the walking of elemental procedure arguments for scalarization. As information about dummy arguments can be obtained from the actual argument through the just-introduced

[PATCH v3 4/5] fortran: Delete redundant missing_arg_type field

Now that we can get information about an actual arg's associated dummy using the associated_dummy attribute, the field missing_arg_type contains redundant information. This removes it. gcc/fortran/ChangeLog: * gfortran.h (gfc_actual_arglist::missing_arg_type): Remove. *

[PATCH v3 2/5] fortran: Reverse actual vs dummy argument mapping

There was originally no way from an actual argument to get to the corresponding dummy argument, even if the job of sorting and matching actual with dummy arguments was done. The closest was a field named actual in gfc_intrinsic_arg that was used as scratch data when sorting arguments of one

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

Hello, This is the third submit of this patch series. After submitting the v2 [2] for master, and a somewhat different variant for backport [3], I thought it was defeating the purpose of the backporting process. So I have decided to rebase the master patches on the backport patches, so that

[PATCH v3 1/5] fortran: Tiny sort_actual internal refactoring

Preliminary refactoring to make further changes more obvious. No functional change. gcc/fortran/ChangeLog: * intrinsic.c (sort_actual): initialise variable and use it earlier. --- gcc/fortran/intrinsic.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git

Re: [PATCH 11/18] rs6000: Builtin expansion, part 6

Hi Segher, Thank you for all of the reviews!  I appreciate your hard work and thorough study of the patches. I've updated these 6 patches and combined them into 1, pushed today.  There are still a couple of cleanups I haven't done, but I made note in the code where these are needed. Thanks

RE: Some PINGs

>On 11/6/2021 4:20 PM, Roger Sayle wrote: >> Simplify paradoxical subreg extensions of TRUNCATE >> https://gcc.gnu.org/pipermail/gcc-patches/2021-September/578848.html > So the discussion seemed to end with a recommendation to try and address this > earlier in the call chain rather than in

Re: [PATCH,FORTRAN] Fix memory leak in finalization wrappers

Le 07/11/2021 à 00:56, Bernhard Reutner-Fischer a écrit : On Sat, 6 Nov 2021 13:04:07 +0100 Mikael Morin wrote: Le 05/11/2021 à 23:08, Bernhard Reutner-Fischer a écrit : On Fri, 5 Nov 2021 19:46:16 +0100 Mikael Morin wrote: I’m a bit concerned by the loss of the null_expr’s type

Fix inter-procedural EAF flags propagation with respect to !binds_to_current_def_p

Hi, while proofreading the code for handling EAF flags of !binds_to_current_def_p I noticed that the interprocedural dataflow actually ignores the flag possibly introducing wrong code on nterposable functions in non-trivial recursion cycles or at ltrans partition boundary. This patch unifies the

Re: Implement intraprocedural dataflow for ipa-modref EAF analyser

Hi, I have commited the patch now. On the current tree the patch causes new failure ./gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/vector_subscript_1.f90 -O1 execution test ./gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/vector_subscript_1.f90 -O2 execution test

Re: [PATCH v4] Fix ICE when mixing VLAs and statement expressions [PR91038]

Am Mittwoch, den 03.11.2021, 10:18 -0400 schrieb Jason Merrill: > On 10/31/21 05:22, Uecker, Martin wrote: > > Hi Jason, > > > > here is the fourth version of the patch. > > > > I followed your suggestion and now make this > > transformation sooner in pointer_int_sum. > > I also added a check to