[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

[Bug middle-end/102906] [12 regression] gcc.target/arm/ivopts-4.c fails since r12-4526

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102906 --- Comment #6 from Christophe Lyon --- (In reply to Aldy Hernandez from comment #5) > (In reply to Christophe Lyon from comment #4) > > If I'm not mistaken, if you click on "REGRESSED" for that specific line, > > you'll see that only

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

[Bug middle-end/102997] [12 Regression] 45% 454.calculix regression with LTO+PGO -march=native -Ofast on Zen since r12-4526-gd8edfadfc7a9795b65177a50ce44fd348858e844

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997 --- Comment #12 from Aldy Hernandez --- It's been mentioned that this SPEC test has irreconcilable differences between the train and peak runs, and cannot be reasonably compared. Is the slowdown reported between two runs of compatible runs

[Bug middle-end/102997] [12 Regression] 45% 454.calculix regression with LTO+PGO -march=native -Ofast on Zen since r12-4526-gd8edfadfc7a9795b65177a50ce44fd348858e844

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997 --- Comment #11 from Aldy Hernandez --- >From what I gather, this is only reproducible with PGO. If so, it may be worth nothing that Jeff has mentioned that the backward threader probably does not do a very good job with keeping profile counts

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,

[Bug middle-end/102906] [12 regression] gcc.target/arm/ivopts-4.c fails since r12-4526

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102906 --- Comment #5 from Aldy Hernandez --- (In reply to Christophe Lyon from comment #4) > If I'm not mistaken, if you click on "REGRESSED" for that specific line, > you'll see that only ssa-dom-thread-7.c actually regressed with the >

[Bug rtl-optimization/103125] stack adjustment with struct with int element on aarch64be-*-*

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103125 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization Ever

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

[Bug rtl-optimization/103125] New: [ARM]Useless stack initialization on aarch64 big-endian

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103125 Bug ID: 103125 Summary: [ARM]Useless stack initialization on aarch64 big-endian Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

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

[Bug tree-optimization/102789] libgomp.c++/simd-3.C fails after r12-4340 for 32 bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102789 Kewen Lin changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

[Bug tree-optimization/102789] libgomp.c++/simd-3.C fails after r12-4340 for 32 bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102789 --- Comment #14 from CVS Commits --- The releases/gcc-11 branch has been updated by Kewen Lin : https://gcc.gnu.org/g:7cb3b868f702e63e53ee1880c6b8a61676144395 commit r11-9219-g7cb3b868f702e63e53ee1880c6b8a61676144395 Author: Kewen Lin Date:

[Bug tree-optimization/102789] libgomp.c++/simd-3.C fails after r12-4340 for 32 bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102789 --- Comment #13 from CVS Commits --- The releases/gcc-10 branch has been updated by Kewen Lin : https://gcc.gnu.org/g:4f024c99a05f1c6852d1e5daad4a172f4cdd24a1 commit r10-10257-g4f024c99a05f1c6852d1e5daad4a172f4cdd24a1 Author: Kewen Lin Date:

[Bug tree-optimization/102789] libgomp.c++/simd-3.C fails after r12-4340 for 32 bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102789 --- Comment #12 from CVS Commits --- The releases/gcc-9 branch has been updated by Kewen Lin : https://gcc.gnu.org/g:6cce26752d8431a1ef6d3f9a97fa0ee2e9f96816 commit r9-9815-g6cce26752d8431a1ef6d3f9a97fa0ee2e9f96816 Author: Kewen Lin Date:

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

[Bug target/103124] PPC: "mr" instruction is unnecessary when extending DI to V1TI

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103124 --- Comment #1 from HaoChen Gui --- Build command gcc -O2 -S test.c -mcpu=power9

[Bug target/103124] PPC: "mr" instruction is unnecessary when extending DI to V1TI

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103124 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement

[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

[Bug target/103124] New: PPC: "mr" instruction is unnecessary when extending DI to V1TI

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103124 Bug ID: 103124 Summary: PPC: "mr" instruction is unnecessary when extending DI to V1TI Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

[Bug c/103123] incorrect or misleading warning "floating constant exceeds range of ..." in ISO C11 and C17

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103123 --- Comment #3 from Andrew Pinski --- Clang produces: :4:10: warning: magnitude of floating-point constant too large for type 'double'; maximum is 1.7976931348623157E+308 [-Wliteral-range] return 1.0e999; ^

[Bug c/103123] incorrect or misleading warning "floating constant exceeds range of ..." in ISO C11 and C17

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103123 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c/103123] incorrect or misleading warning "floating constant exceeds range of ..." in ISO C11 and C17

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103123 --- Comment #1 from Andrew Pinski --- The code in GCC: /* Both C and C++ require a diagnostic for a floating constant outside the range of representable values of its type. Since we have __builtin_inf* to produce an infinity, this

[Bug c/103123] New: incorrect or misleading warning "floating constant exceeds range of ..." in ISO C11 and C17

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103123 Bug ID: 103123 Summary: incorrect or misleading warning "floating constant exceeds range of ..." in ISO C11 and C17 Product: gcc Version: 12.0 Status: UNCONFIRMED

[Bug tree-optimization/103122] [12 Regression] ICE in fill_block_cache, at gimple-range-cache.cc:1277 with -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103122 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |12.0

[Bug target/103090] [i386] GCC should use the SF and ZF flags in some atomic_fetch_op sequences

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103090 --- Comment #2 from Hongtao.liu --- Similar like Jakub did in r7-532, We need another IFN & optab to do the optimization. The IFN and optab is like atomic_logic_test_and_set_sf which used to perform logic operation and set SF.

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. >

[Bug tree-optimization/103077] [12 Regression] -ftree-loop-vectorize and -ftree-slp-vectorize are enabled at -O2 but their documentation says they are only enabled at -O3 and above

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103077 Hongtao.liu changed: What|Removed |Added CC||crazylht at gmail dot com --- Comment #3

[Bug tree-optimization/103077] [12 Regression] -ftree-loop-vectorize and -ftree-slp-vectorize are enabled at -O2 but their documentation says they are only enabled at -O3 and above

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103077 --- Comment #2 from CVS Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:ae1de0bf72fca92f94a7e29f51ce4448b877db4a commit r12-4986-gae1de0bf72fca92f94a7e29f51ce4448b877db4a Author: liuhongt Date: Fri Nov

[Bug middle-end/102464] Miss optimization for (_Float16) sqrtf ((float) f16)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102464 --- Comment #13 from CVS Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:a1f7ead09cd41d32e2fe902eb32e587c36e7 commit r12-4985-ga1f7ead09cd41d32e2fe902eb32e587c36e7 Author: liuhongt Date: Mon

[Bug middle-end/102464] Miss optimization for (_Float16) sqrtf ((float) f16)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102464 --- Comment #12 from CVS Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:2ad1e8081f4797a99a96b513ffe14c7305e9b3d8 commit r12-4984-g2ad1e8081f4797a99a96b513ffe14c7305e9b3d8 Author: liuhongt Date: Mon

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

[Bug tree-optimization/103122] New: [12 Regression] ICE in fill_block_cache, at gimple-range-cache.cc:1277 with -O2

bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. GCC version: gcc version 12.0.0 20211107 (9defce622893f87d954e0089e0ea79e1e388a480) (GCC)

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

[Bug fortran/103054] [f18] Gfortran accepts invalid and rejects valid co_reduce argument keyword name

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103054 Thomas Koenig changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

gcc-12-20211107 is now available

Snapshot gcc-12-20211107 is now available on https://gcc.gnu.org/pub/gcc/snapshots/12-20211107/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 12 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

[Bug other/103121] New: Warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121 Bug ID: 103121 Summary: Warnings Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned

[Bug tree-optimization/103120] [12 Regression] test miscompiled with -O2 since r12-4790

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120 Andrew Pinski changed: What|Removed |Added Severity|normal |blocker --- Comment #4 from Andrew

[Bug tree-optimization/103120] [12 Regression] test miscompiled with -O2 since r12-4790

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120 Andrew Pinski changed: What|Removed |Added Target|x86_64-linux-gnu, |

[Bug tree-optimization/98925] Extend ipa-prop to handle return functions for slot optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98925 Jan Hubicka changed: What|Removed |Added Summary|Extend modref to handle |Extend ipa-prop to handle

[Bug tree-optimization/103120] [12 Regression] test miscompiled with -O2 on darwin since r12-4790

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120 Iain Buclaw changed: What|Removed |Added Target|x86_64-lin ux-gnu |x86_64-linux-gnu, |

[Bug ipa/103055] [12 Regression] ICE: in get_ssa_name_flags, at ipa-modref.c:1660 with --param=modref-max-depth=0 since r12-4852-g18f0873d1e595dc2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103055 Jan Hubicka changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug tree-optimization/103120] [12 Regression] test miscompiled with -O2 on darwin since r12-4790

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |12.0 Component|middle-end

[Bug middle-end/103120] New: [12 Regression] test miscompiled with -O2 on darwin since r12-4790

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120 Bug ID: 103120 Summary: [12 Regression] test miscompiled with -O2 on darwin since r12-4790 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

[Bug ipa/103055] [12 Regression] ICE: in get_ssa_name_flags, at ipa-modref.c:1660 with --param=modref-max-depth=0 since r12-4852-g18f0873d1e595dc2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103055 --- Comment #3 from CVS Commits --- The master branch has been updated by Jan Hubicka : https://gcc.gnu.org/g:87e57378ba554212a32a0743fee03481d1289318 commit r12-4981-g87e57378ba554212a32a0743fee03481d1289318 Author: Jan Hubicka Date: Sun

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.

[Bug fortran/102816] [12 Regression] ICE in resolve_structure_cons, at fortran/resolve.c:1467 since r12-4452-g1e819bd95ebeefc1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102816 --- Comment #4 from CVS Commits --- The releases/gcc-11 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:3371e7f18df52867b0b88966bd98d3f1eff6f815 commit r11-9217-g3371e7f18df52867b0b88966bd98d3f1eff6f815 Author: Harald Anlauf

[Bug fortran/102685] [12 Regression] ICE in output_constructor_regular_field, at varasm.c:5514 since r12-4278-g74ccca380cde5e79

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102685 --- Comment #9 from CVS Commits --- The releases/gcc-11 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:b1cab51131ad4d5501bf3f01e694704142a10c1a commit r11-9216-gb1cab51131ad4d5501bf3f01e694704142a10c1a Author: Harald Anlauf

[Bug fortran/102715] [12 Regression] ICE in gfc_simplify_transpose, at fortran/simplify.c:8184 since r12-4278-g74ccca380cde5e79

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102715 --- Comment #4 from CVS Commits --- The releases/gcc-11 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:db1da3d37e33b0adcd7fed68cfdb96e8ee265ccf commit r11-9215-gdb1da3d37e33b0adcd7fed68cfdb96e8ee265ccf Author: Harald Anlauf

[Bug fortran/102817] [12 Regression] ICE in gfc_clear_shape, at fortran/expr.c:422 since r12-4278-g74ccca380cde5e79

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102817 --- Comment #8 from CVS Commits --- The releases/gcc-11 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:907fd5049735ed1bd17e221db5a812dedee5dfc8 commit r11-9214-g907fd5049735ed1bd17e221db5a812dedee5dfc8 Author: Harald Anlauf

[Bug fortran/99348] ICE in resolve_structure_cons, at fortran/resolve.c:1286

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99348 --- Comment #6 from CVS Commits --- The releases/gcc-11 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:1b740d8000cac8048c728fb0bd75c7146429 commit r11-9213-g1b740d8000cac8048c728fb0bd75c7146429 Author: Harald Anlauf

[Bug fortran/102521] ICE in gfc_conv_array_initializer, at fortran/trans-array.c:6240

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102521 --- Comment #7 from CVS Commits --- The releases/gcc-11 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:1b740d8000cac8048c728fb0bd75c7146429 commit r11-9213-g1b740d8000cac8048c728fb0bd75c7146429 Author: Harald Anlauf

[Bug fortran/103054] [f18] Gfortran accepts invalid and rejects valid co_reduce argument keyword name

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103054 --- Comment #5 from anlauf at gcc dot gnu.org --- Please have a look at the testsuite, too.

[Bug middle-end/96159] atomic creates incorrect code for possible isaligned struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96159 --- Comment #4 from Andrew Pinski --- So it looks like __atomic_load assumes the type is _Atomic which has the right alignment to it.

[Bug tree-optimization/103111] bogus stringop overflow warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103111 Martin Sebor changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #41 from cqwrteur --- (In reply to Andrew Aladjev from comment #38) > Sure, patches works perfect. But we need somehow decrease the chance of > similar regressions in future. It is possible by adding any basic "canadian" > build

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #40 from cqwrteur --- (In reply to Andrew Aladjev from comment #38) > Sure, patches works perfect. But we need somehow decrease the chance of > similar regressions in future. It is possible by adding any basic "canadian" > build

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #39 from cqwrteur --- (In reply to Andrew Aladjev from comment #38) > Sure, patches works perfect. But we need somehow decrease the chance of > similar regressions in future. It is possible by adding any basic "canadian" > build

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #38 from Andrew Aladjev --- Sure, patches works perfect. But we need somehow decrease the chance of similar regressions in future. It is possible by adding any basic "canadian" build into the list of tests to be done before release.

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #37 from cqwrteur --- (In reply to cqwrteur from comment #36) > (In reply to Andrew Aladjev from comment #35) > > Hello cqwrteur, do you have an influence on core gcc developers? Please > > provide an idea to add at least one

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #36 from cqwrteur --- (In reply to Andrew Aladjev from comment #35) > Hello cqwrteur, do you have an influence on core gcc developers? Please > provide an idea to add at least one "canadian" test before release. >

[Bug tree-optimization/103119] New: ICE in get_imports, at gimple-range-gori.cc:230

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103119 Bug ID: 103119 Summary: ICE in get_imports, at gimple-range-gori.cc:230 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #35 from Andrew Aladjev --- Hello cqwrteur, do you have an influence on core gcc developers? Please provide an idea to add at least one "canadian" test before release. x86_64-pc-linux-gnu -> x86_64-unknown-linux-gnu will be enough.

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #34 from cqwrteur --- Created attachment 51747 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51747=edit Correct Patch by just fixing configure and configure.ac with -nostdinc++ Tested with over 20 canadian cross builds

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #33 from cqwrteur --- (In reply to Andrew Aladjev from comment #32) > I've added include_next_fenv dirty patch. I want just to quickly explain how > to use it. > > First of all I've noticed (many years ago) that gcc developers are

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #32 from Andrew Aladjev --- I've added include_next_fenv dirty patch. I want just to quickly explain how to use it. First of all I've noticed (many years ago) that gcc developers are making releases based on limited set of basic

[Bug tree-optimization/102943] [12 Regression] Jump threader compile-time hog with 521.wrf_r

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102943 --- Comment #27 from hubicka at kam dot mff.cuni.cz --- > > This PR is still open, at least for slowdown in the threader with LTO. The > issue is ranger wide, so it may also cause slowdowns on non-LTO builds for > WRF, though I haven't

Re: [Bug tree-optimization/102943] [12 Regression] Jump threader compile-time hog with 521.wrf_r

> > This PR is still open, at least for slowdown in the threader with LTO. The > issue is ranger wide, so it may also cause slowdowns on non-LTO builds for > WRF, though I haven't checked. I just wanted to record the fact somewhere since I was looking up the revision range mostly to figure out

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #31 from cqwrteur --- (In reply to Andrew Aladjev from comment #30) > Created attachment 51746 [details] > Include fenv dirty patch for gcc 11.2.0 > > Please apply carefully, it is not safe. no. adding -nostdinc++ is the right

[Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 --- Comment #30 from Andrew Aladjev --- Created attachment 51746 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51746=edit Include fenv dirty patch for gcc 11.2.0 Please apply carefully, it is not safe.

[Bug c++/103118] New: [modules] ICE tree check in get_merge_kind at cp/module.cc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103118 Bug ID: 103118 Summary: [modules] ICE tree check in get_merge_kind at cp/module.cc Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-on-valid-code

[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

[Bug tree-optimization/102943] [12 Regression] Jump threader compile-time hog with 521.wrf_r

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102943 --- Comment #26 from Aldy Hernandez --- (In reply to Jan Hubicka from comment #25) > LNT sees new regresion on WRF build times (around 6%) at Nov 3 > > https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=287.548.8 >

[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:

[Bug fortran/101337] gfortran doesn't diagnose all operands with constraint violations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101337 sandra at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug fortran/101337] gfortran doesn't diagnose all operands with constraint violations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101337 --- Comment #4 from CVS Commits --- The master branch has been updated by Sandra Loosemore : https://gcc.gnu.org/g:ee11be7f2d788e6055ebed9746a8d8ac3cb04b8e commit r12-4979-gee11be7f2d788e6055ebed9746a8d8ac3cb04b8e Author: Sandra Loosemore

[Bug fortran/89078] [meta-bug] Improve the gfortran manual

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89078 --- Comment #2 from sandra at gcc dot gnu.org --- I did look over the entire list of still-open issues and did not see any further low-hanging fruit. It also seemed to me that some of the issues on the list are cases where it appears the

[Bug tree-optimization/102943] [12 Regression] Jump threader compile-time hog with 521.wrf_r

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102943 --- Comment #25 from Jan Hubicka --- LNT sees new regresion on WRF build times (around 6%) at Nov 3 https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=287.548.8 https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=289.270.8 The

[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

[Bug target/103095] Option to force no overalignment

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103095 Andrew Pinski changed: What|Removed |Added Status|REOPENED|UNCONFIRMED Ever confirmed|1

[Bug fortran/103054] [f18] Gfortran accepts invalid and rejects valid co_reduce argument keyword name

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103054 --- Comment #4 from kargl at gcc dot gnu.org --- Created attachment 51745 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51745=edit documentation update Forgot the documentation part of the patch.

[Bug tree-optimization/103117] New: uncprop produces harder to analyze but not better code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103117 Bug ID: 103117 Summary: uncprop produces harder to analyze but not better code Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3

  1   2   >