public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/100948] [12 Regression] ICE in gfc_conv_expr_val, at fortran/trans-expr.c:9069 Date: Mon, 07 Jun 2021 18:02:54 +0000 [thread overview] Message-ID: <bug-100948-4-2Llcl4NCNV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100948-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100948 G. Steinmetz <gscfq@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code --- Comment #1 from G. Steinmetz <gscfq@t-online.de> --- Additionally a better/valid example : $ cat z3.f90 program p type t character(:), allocatable :: c(:) end type type(t), allocatable :: x x = t(['abc', 'uvw']) associate (y => x%c(:)(:)) print *, y end associate end # should print : abcuvw
next prev parent reply other threads:[~2021-06-07 18:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-07 17:31 [Bug fortran/100948] New: " gscfq@t-online.de 2021-06-07 18:02 ` gscfq@t-online.de [this message] 2021-06-07 19:34 ` [Bug fortran/100948] " anlauf at gcc dot gnu.org 2021-06-07 19:36 ` anlauf at gcc dot gnu.org 2021-06-11 12:37 ` marxin at gcc dot gnu.org 2021-06-11 15:33 ` jrfsousa at gcc dot gnu.org 2021-06-13 19:15 ` jrfsousa at gcc dot gnu.org 2021-06-13 19:16 ` jrfsousa at gcc dot gnu.org 2022-01-17 14:37 ` rguenth at gcc dot gnu.org 2022-05-06 8:30 ` [Bug fortran/100948] [12/13 " jakub at gcc dot gnu.org 2023-04-08 8:04 ` cvs-commit at gcc dot gnu.org 2023-04-08 9:33 ` pault 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-100948-4-2Llcl4NCNV@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).