[Bug target/96072] New: ICE: Segmentation fault (in add_reg_note)

2020-07-05 Thread asolokha at gmx dot com
: Segmentation fault 24 | } | ^ 0xe74ba6 crash_signal /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/toplev.c:328 0xe09f99 add_reg_note(rtx_def*, reg_note, rtx_def*) /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc

[Bug fortran/96071] New: ICE in matching_typebound_op, at fortran/interface.c:4233

2020-07-05 Thread asolokha at gmx dot com
951: internal compiler error: in matching_typebound_op, at fortran/interface.c:4233 0x599046 matching_typebound_op /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/fortran/interface.c:4233 0x87e754 gfc_extend_expr(gfc_expr*) /var/tmp/port

[Bug tree-optimization/92860] [8/9/10/11 regression] Global flags affected by -O settings are clobbered by optimize attribute

2020-07-05 Thread asolokha at gmx dot com
9 0x9196b6 handle_pragma_pop_options /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/c-family/c-pragma.c:1090 0x895510 c_parser_pragma /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/c/

Re: How to forbid register allocator to overlap bewteen DEST and SOURCE

2020-07-05 Thread jiejie_rong
Hi, Thanks for your reply :) Maybe there are some register limits in reload pass with my case like We need to expand to ‘mov’ and ‘madd’ first to get suitable registers. —Jojo 在 2020年7月3日 +0800 AM5:35,Jim Wilson ,写道: > On Wed, Jul 1, 2020 at 8:40 PM wrote: > > GCC

Delivery report

2020-07-05 Thread postmaster--- via Gcc
Hello, this is the mail server on mail0.airrepcirinc.com. I am sending you this message to inform you on the delivery status of a message you previously sent. Immediately below you will find a list of the affected recipients; also attached is a Delivery Status Notification (DSN) report in

[PATCH] rs6000: Split movsf_from_si from high word before reload[PR89310]

2020-07-05 Thread Xionghu Luo via Gcc-patches
For extracting high part element from DImode register like: {%1:SF=unspec[r122:DI>>0x20#0] 86;clobber scratch;} split it before reload with "and mask" to avoid generating shift right 32 bit then shift left 32 bit. srdi 3,3,32 sldi 9,3,32 mtvsrd 1,9 xscvspdpn 1,1 => rldicr 3,3,0,31 mtvsrd 1,3

[Bug libstdc++/96070] New: std::views::* won't work with non-legacy iterators

2020-07-05 Thread gcc-bugs at marehr dot dialup.fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96070 Bug ID: 96070 Summary: std::views::* won't work with non-legacy iterators Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3

RFC: make combine do as advertised (cheaper-than)?

2020-07-05 Thread Hans-Peter Nilsson via Gcc-patches
Most comments, including the second sentence in the head comment of combine_validate_cost, the main decision-maker of the combine pass, refer to the function as returning true if the new insns(s) *cheaper* than the old insns, when in fact the function returned true also if the cost was the same.

[PATCH] Enable GCC support for AMX

2020-07-05 Thread Hongyu Wang via Gcc-patches
Hi: This patch is about to support Intel Advanced Matrix Extensions (AMX) which will be enabled in GLC. AMX is a new 64-bit programming paradigm consisting of two compo nents: a set of 2-dimensional registers (tiles) representing sub-arrays from a larger 2-dimensional memory image, and an

Re: [PATCH] analyzer: Fix -Wanalyzer-possible-null-argument warning

2020-07-05 Thread David Malcolm via Gcc-patches
On Wed, 2020-07-01 at 18:29 +0100, Jonathan Wakely wrote: > On 30/06/20 17:43 +0100, Jonathan Wakely wrote: > > gcc/testsuite/ChangeLog: > > > > * g++.dg/analyzer/pr94028.C: Make operator new non-throwing so > > that the compiler doesn't implicitly mark it as returning > > non-null. >

Re: [PATCH] Map filename from print in gfortran with -ffile-prefix-map (PR96069)

2020-07-05 Thread Yichao Yu via Gcc-patches
> I think this remapping should happen with `file-prefix-map` but > shouldn't with `debug-prefix-map` (though if it happens for both it's > also not too bad) and I believe this patch is the minimum change to > achieve that. I think it makes sense to make this follow > `macro-prefix-map` although

RFA: Fix combine.c combining a move and a non-move into two non-moves, PR93372

2020-07-05 Thread Hans-Peter Nilsson via Gcc-patches
TL;DR: fixing a misdetection of what is a "simple move". Looking into performace degradation after de-cc0 for CRIS, I noticed combine behaving badly; it changed a move and a right-shift into two right-shifts, where the "combined" move was not eliminated in later passes, and where the deficiency

[PATCH] Map filename from print in gfortran with -ffile-prefix-map (PR96069)

2020-07-05 Thread Yichao Yu via Gcc-patches
Sorry I think I accidentally had rich text mode on and also forgot the `[PATCH]` in the title in the previous email... Try again... Currently this is using the macro prefix map without allowing the -fmacro-prefix-map argument, which is arguably pretty weird... but I don't know what would be a

Map filename from print in gfortran with -ffile-prefix-map (PR96069)

2020-07-05 Thread Yichao Yu via Gcc-patches
Currently this is using the macro prefix map without allowing the ---fmacro-prefix-map argument, which is arguably pretty weird... but I don't know what would be a better way. I think this remapping should happen with `file-prefix-map` but shouldn't with `debug-prefix-map` (though if it happens

committed: cris: New peephole2 movulsr + test-case.

2020-07-05 Thread Hans-Peter Nilsson via Gcc-patches
(The previous patch was also committed, FWIW, I just forgot to mention it.) Combine likes to change a zero-extension / and + shift as seen in the test-case source to a logical shift followed by an and of the shifted mask, like: lsrq 1,r0 and.d 0x7f,r0 This was observed in the hot loop of

cris: Correct gcc_assert for atomic_fetch_op pattern

2020-07-05 Thread Hans-Peter Nilsson via Gcc-patches
Yet another misnumbering of operands: the asserted non-overlap would be the only benign operands overlap. "Suddenly" exposed by g++.dg/cpp0x/pr81325.C when testing unrelated changes affecting register allocation. To wit, operands 2 and 1 are the only ones that are safe for overlap, it's only

committed: cris: update recent patterns. Simplify cris_select_cc_mode.

2020-07-05 Thread Hans-Peter Nilsson via Gcc-patches
The code in cris_select_cc_mode for selecting CC_NZmode was partly inconsistent with the comment and partly seemed ambiguous. I couldn't find a reason why I qualified selection of CC_NZmode on the setting operation once a matching user was spotted, so I just removed that. The cris.c update was

committed: cris.md: Reinstate add/sub with extend

2020-07-05 Thread Hans-Peter Nilsson via Gcc-patches
When cleaning out the multitude of patterns with unknown coverage, this one went the way of the bathwater. It's use is barely common enough to mark when diffing libgcc, and has a minimal impact on performance-testsuites. Anyway, reinstated with a couple of test-cases. It's suboptimal of

gcc-11-20200705 is now available

2020-07-05 Thread GCC Administrator via Gcc
Snapshot gcc-11-20200705 is now available on https://gcc.gnu.org/pub/gcc/snapshots/11-20200705/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 11 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: [PATCH] PR fortran/95980 - ICE in get_unique_type_string, at fortran/class.c:485

2020-07-05 Thread Harald Anlauf
Early ping. > Gesendet: Montag, 29. Juni 2020 um 22:58 Uhr > Von: "Harald Anlauf" > An: "fortran" , "gcc-patches" > Betreff: [PATCH] PR fortran/95980 - ICE in get_unique_type_string, at > fortran/class.c:485 > > Dear all, > > here's a couple of NULL pointer dereferences on invalid code. > >

Re: [wwwdocs] Document new G++ features

2020-07-05 Thread Gerald Pfeifer
On Fri, 3 Jul 2020, Marek Polacek via Gcc-patches wrote: > Pushed. Nice. And thanks for doing this along the way. That's beneficial for users/testers of GCC 11 as it evolves, and also helps not forget things during the release process. Gerald

[Bug target/95581] [11 Regression] ICE in gimple_call_arg, at gimple.h:3260 since r11-959-gb825a22890740f341eae566af27e18e528cd29a7

2020-07-05 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95581 --- Comment #12 from Segher Boessenkool --- This is pre-approved with a testcase (if it fixes that testcase, etc., yadda yadda). Thanks!

[Bug fortran/89574] [8/9/10/11 Regression] internal compiler error: in conv_function_val, at fortran/trans-expr.c:3792

2020-07-05 Thread anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89574 --- Comment #7 from anlauf at gcc dot gnu.org --- Two slightly reduced testcase variants that ICE with current master: % cat pr89574-red1.f90 module mod contains subroutine init end subroutine end module mod module init use mod, only :

[Bug fortran/96069] New: -ffile-prefix-map does not affect print in gfortran

2020-07-05 Thread yyc1992 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96069 Bug ID: 96069 Summary: -ffile-prefix-map does not affect print in gfortran Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug target/96062] Partial register stall caused by avoidable use of SETcc, and useless MOVZBL

2020-07-05 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96062 --- Comment #1 from Uroš Bizjak --- (In reply to Joseph C. Sible from comment #0) > Consider this C code: > > long ps4_syscall0(long n) { > long ret; > int carry; > __asm__ __volatile__( > "syscall" > : "=a"(ret),

[Bug fortran/87477] [meta-bug] [F03] issues concerning the ASSOCIATE statement

2020-07-05 Thread anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87477 Bug 87477 depends on bug 88379, which changed state. Bug 88379 Summary: [8/9 Regression] [Coarray] ICE with allocatable coarray, class and associate in resolve_assoc_var, at fortran/resolve.c:8750

[Bug fortran/83700] [Meta-bug] Fortran Coarray issues

2020-07-05 Thread anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83700 Bug 83700 depends on bug 88379, which changed state. Bug 88379 Summary: [8/9 Regression] [Coarray] ICE with allocatable coarray, class and associate in resolve_assoc_var, at fortran/resolve.c:8750

[Bug fortran/88379] [8/9 Regression] [Coarray] ICE with allocatable coarray, class and associate in resolve_assoc_var, at fortran/resolve.c:8750

2020-07-05 Thread anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88379 anlauf at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED

[Bug fortran/88379] [8/9 Regression] [Coarray] ICE with allocatable coarray, class and associate in resolve_assoc_var, at fortran/resolve.c:8750

2020-07-05 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88379 --- Comment #9 from CVS Commits --- The releases/gcc-8 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:56ce663146b436ff1a267ee2a9701b7d5e190e62 commit r8-10344-g56ce663146b436ff1a267ee2a9701b7d5e190e62 Author: Harald Anlauf

[Bug fortran/88379] [8/9 Regression] [Coarray] ICE with allocatable coarray, class and associate in resolve_assoc_var, at fortran/resolve.c:8750

2020-07-05 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88379 --- Comment #8 from CVS Commits --- The releases/gcc-9 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:4e9e0dab7a1dd9003269a8663117135f9ad91a94 commit r9-8720-g4e9e0dab7a1dd9003269a8663117135f9ad91a94 Author: Harald Anlauf

[Bug fortran/27318] gfortran should warn if a interface does not match

2020-07-05 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27318 Thomas Koenig changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug fortran/29670] [meta-bug] fortran interfaces

2020-07-05 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29670 Bug 29670 depends on bug 27318, which changed state. Bug 27318 Summary: gfortran should warn if a interface does not match https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27318 What|Removed |Added

Re: *ping* [patch, fortran] PR 27318, warn if interfaces do not match

2020-07-05 Thread Thomas Koenig
Hi Paul and Dominique, The patch looks fine to me. If Dominique has nothing to report then it is OK for trunk. committed. Thanks! Regards Thomas

[Bug fortran/27318] gfortran should warn if a interface does not match

2020-07-05 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27318 --- Comment #6 from CVS Commits --- The master branch has been updated by Thomas Kथà¤nig : https://gcc.gnu.org/g:cc9a9229285a26ac12bc8de53237ce9c4d42f867 commit r11-1814-gcc9a9229285a26ac12bc8de53237ce9c4d42f867 Author: Thomas Koenig Date:

[Bug fortran/96018] Optimization issue with external HDF5 library

2020-07-05 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96018 --- Comment #8 from Thomas Koenig --- Comment on attachment 48817 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48817 Minimal example to demonstrate the issue. Hm, I cannot reproduce this because I do not have the hdf5 library installed.

[Bug fortran/95366] [10/11 Regression] TYPE IS(character(*)) no longer matches since r10-3605-gf61e54e59cda5a2e

2020-07-05 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95366 Thomas Koenig changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug fortran/95366] [10/11 Regression] TYPE IS(character(*)) no longer matches since r10-3605-gf61e54e59cda5a2e

2020-07-05 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95366 --- Comment #9 from CVS Commits --- The releases/gcc-10 branch has been updated by Thomas Kथà¤nig : https://gcc.gnu.org/g:858b288d2a6afc2f71f817344be3af4b7c3d4b3f commit r10-8427-g858b288d2a6afc2f71f817344be3af4b7c3d4b3f Author: Thomas

[Bug c++/96068] New: Extra semicolon outside of a function should be allowed after c++11?

2020-07-05 Thread haoxintu at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96068 Bug ID: 96068 Summary: Extra semicolon outside of a function should be allowed after c++11? Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: diagnostic

Re: Local optimization options

2020-07-05 Thread Marc Glisse
On Sun, 5 Jul 2020, Thomas König wrote: Am 04.07.2020 um 19:11 schrieb Richard Biener : On July 4, 2020 11:30:05 AM GMT+02:00, "Thomas König" wrote: What could be a preferred way to achieve that? Could optimization options like -ffast-math be applied to blocks instead of functions? Could

[Bug jit/96067] New: __atomic_compare_exchange_n should return bool instead of void

2020-07-05 Thread bouanto at zoho dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96067 Bug ID: 96067 Summary: __atomic_compare_exchange_n should return bool instead of void Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal

[Bug jit/96066] New: Cannot use values from some builtins because they are of void type

2020-07-05 Thread bouanto at zoho dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96066 Bug ID: 96066 Summary: Cannot use values from some builtins because they are of void type Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal

Re: Local optimization options

2020-07-05 Thread Richard Biener via Gcc
On July 5, 2020 12:37:58 PM GMT+02:00, "Thomas König" wrote: > >> Am 04.07.2020 um 19:11 schrieb Richard Biener >: >> >> On July 4, 2020 11:30:05 AM GMT+02:00, "Thomas König" > wrote: >>> >>> What could be a preferred way to achieve that? Could optimization >>> options like -ffast-math be

Re: [PATCH] nvptx: Add support for vadd.add and vsub.add instructions

2020-07-05 Thread Tom de Vries
[ fixed $subject ] On 7/3/20 7:20 PM, Roger Sayle wrote: > > The following patch adds support for three-input addition instructions to the > nvptx backend. > The PTX ISA's "vadd.u32.u32.u32.add d, a, b, c" instruction effectively > implements 32-bit d = a+b+c, > and the "vsub.u32.u32.u32

Re: Local optimization options

2020-07-05 Thread Thomas König
> Am 04.07.2020 um 19:11 schrieb Richard Biener : > > On July 4, 2020 11:30:05 AM GMT+02:00, "Thomas König" > wrote: >> >> What could be a preferred way to achieve that? Could optimization >> options like -ffast-math be applied to blocks instead of functions? >> Could we set flags on the

[Bug c++/96065] Move elision of returned automatic variable doesn't happen the variable is enclosed in a block

2020-07-05 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96065 Marc Glisse changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/51571] No named return value optimization while adding a dummy scope

2020-07-05 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51571 Marc Glisse changed: What|Removed |Added CC||b7.10110111 at gmail dot com --- Comment

[Bug target/95581] [11 Regression] ICE in gimple_call_arg, at gimple.h:3260 since r11-959-gb825a22890740f341eae566af27e18e528cd29a7

2020-07-05 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95581 --- Comment #11 from Iain Sandoe --- (In reply to Bill Seurer from comment #10) > I think this will work but haven't had a chance to try it except on the one > power 7 system. Hi Bill - thanks for the patch. This allowed bootstrap to complete

[Bug c++/96065] New: Move elision of returned automatic variable doesn't happen the variable is enclosed in a block

2020-07-05 Thread b7.10110111 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96065 Bug ID: 96065 Summary: Move elision of returned automatic variable doesn't happen the variable is enclosed in a block Product: gcc Version: 10.1.0 Status: UNCONFIRMED

[Bug c++/96064] New: Defaulted constexpr spaceship operator triggers internal compiler error after including utility

2020-07-05 Thread milasudril at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96064 Bug ID: 96064 Summary: Defaulted constexpr spaceship operator triggers internal compiler error after including utility Product: gcc Version: 10.1.0 Status: UNCONFIRMED