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/103137] [12 Regression] ICE in gfc_simplify_transpose, at fortran/simplify.c:8181 Date: Mon, 08 Nov 2021 22:10:40 +0000 [thread overview] Message-ID: <bug-103137-4-9KRuoEwKaX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103137-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103137 --- Comment #2 from anlauf at gcc dot gnu.org --- After playing with the Intel compiler, which accepts the testcase, I start to think the code could actually be valid F2018. At least I cannot find text in the F2018 standard prohibiting PARAMETER for polymorphic variables. So while the patch in comment#1 fixes the regression (ICE), it is far from complete.
next prev parent reply other threads:[~2021-11-08 22:10 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-08 18:36 [Bug fortran/103137] New: " gscfq@t-online.de 2021-11-08 20:50 ` [Bug fortran/103137] " anlauf at gcc dot gnu.org 2021-11-08 22:10 ` anlauf at gcc dot gnu.org [this message] 2021-11-09 8:32 ` [Bug fortran/103137] [12 Regression] ICE in gfc_simplify_transpose, at fortran/simplify.c:8181 since r12-4967-gbcf3728abe848888 marxin at gcc dot gnu.org 2021-11-09 11:24 ` rguenth at gcc dot gnu.org 2021-11-09 11:24 ` rguenth at gcc dot gnu.org 2021-11-10 19:42 ` cvs-commit at gcc dot gnu.org 2021-11-11 20:17 ` cvs-commit at gcc dot gnu.org 2021-11-13 20:15 ` cvs-commit at gcc dot gnu.org 2021-11-15 18:24 ` gscfq@t-online.de 2022-05-06 8:31 ` [Bug fortran/103137] [12/13 " jakub at gcc dot gnu.org 2022-06-30 19:01 ` cvs-commit at gcc dot gnu.org 2022-07-03 19:44 ` cvs-commit at gcc dot gnu.org 2022-07-03 20:13 ` cvs-commit at gcc dot gnu.org 2022-07-03 20:29 ` cvs-commit at gcc dot gnu.org 2022-07-03 20:31 ` anlauf 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-103137-4-9KRuoEwKaX@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).