public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/102314] [12 Regression] ICE in verify_ssa, at tree-ssa.c:1076 since r12-1319-gd4d38135b3137f1d Date: Tue, 22 Mar 2022 13:58:50 +0000 [thread overview] Message-ID: <bug-102314-4-UU4psw9ZYl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102314-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102314 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I think those types: character(kind=1)[1:.y] * y; don't really make sense for the character(:) allocatables, I think much better would be to leave the TYPE_MAX_VALUE from TYPE_DOMAIN out, making it [1:]. [1:.y] nicely expresses the intent, in most places y (if it is not NULL) should point to [1:.y] array. But if we emit a DECL_EXPR for it, it will be just wrong, the middle-end expects the C/C++ VLA behavior, the size is computed once (when encountering the DECL_EXPR), then the VLA is allocated with it and that is the size it has from that point on. The deferred-length (is that the right term) arrays work differently from this though, the length can be changed at any time. So the VLA length is always determined from the current value of the .y variable (except in the short spots where that is updated and the var not yet reallocated).
next prev parent reply other threads:[~2022-03-22 13:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-13 17:30 [Bug fortran/102314] New: [11/12 Regression] ICE in verify_ssa, at tree-ssa.c:1076 gscfq@t-online.de 2021-09-14 7:03 ` [Bug fortran/102314] " rguenth at gcc dot gnu.org 2021-09-14 7:26 ` [Bug fortran/102314] [12 Regression] ICE in verify_ssa, at tree-ssa.c:1076 since r12-1319-gd4d38135b3137f1d marxin at gcc dot gnu.org 2022-01-20 10:01 ` rguenth at gcc dot gnu.org 2022-03-22 13:58 ` jakub at gcc dot gnu.org [this message] 2022-03-22 14:13 ` jakub at gcc dot gnu.org 2022-04-04 13:06 ` rguenth at gcc dot gnu.org 2022-05-06 8:31 ` [Bug fortran/102314] [12/13 " jakub at gcc dot gnu.org 2023-05-08 12:22 ` [Bug fortran/102314] [12/13/14 Regression] ICE in verify_ssa, at tree-ssa.c:1076 since r12-1319-gd4d38135b3137f1d – with deferred-length character variable 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-102314-4-UU4psw9ZYl@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).