public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/104684] [10/11/12/13 Regression] ICE: 'verify_gimple' failed (Error: non-trivial conversion in 'component_ref') since r7-5771-gde91486c745d5ff6 Date: Wed, 06 Jul 2022 18:45:01 +0000 [thread overview] Message-ID: <bug-104684-4-QGmfAlegOk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104684-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104684 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code --- Comment #4 from anlauf at gcc dot gnu.org --- Interesting. Replacing buffer%array => this%send_index by buffer%array => this%send_index(:) avoids the ICE.
next prev parent reply other threads:[~2022-07-06 18:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-25 11:08 [Bug fortran/104684] New: ICE: 'verify_gimple' failed (Error: non-trivial conversion in 'component_ref') asolokha at gmx dot com 2022-02-25 12:58 ` [Bug fortran/104684] [9/10/11/12 Regression] ICE: 'verify_gimple' failed (Error: non-trivial conversion in 'component_ref') since r7-5771-gde91486c745d5ff6 marxin at gcc dot gnu.org 2022-03-09 9:34 ` rguenth at gcc dot gnu.org 2022-05-27 9:47 ` [Bug fortran/104684] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2022-07-06 18:45 ` anlauf at gcc dot gnu.org [this message] 2022-07-06 20:13 ` anlauf at gcc dot gnu.org 2023-07-07 10:42 ` [Bug fortran/104684] [11/12/13/14 " rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-104684-4-QGmfAlegOk@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).