public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/104430] [10 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 since r9-3522-gd0477233215e37de Date: Fri, 26 Aug 2022 10:59:48 +0000 [thread overview] Message-ID: <bug-104430-4-vnGRnmTtpt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104430-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104430 --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- The patch also fixes an ICE for this code, taken from https://stackoverflow.com/q/73498995/981959 program main integer, dimension(1:2) :: iii real, dimension(1:4,1:4,1:2) :: myArray associate(iix => iii(1), iiy=> iii(2) ) forall( iix=1:4, iiy=1:4 ) myArray(iix,iiy,1) = iix + iiy myArray(iix,iiy,2) = (iix + iiy)*10 endforall end associate print *, myArray(:,:,1) print *, myArray(:,:,2) end program main I know nothing about Fortran, but it looks sufficiently different to me that maybe it's worth adding another test based on this code, so we don't regress. The question of whether to backport to gcc-10 or close this is still waiting for an answer too.
next prev parent reply other threads:[~2022-08-26 10:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-07 18:49 [Bug fortran/104430] New: [9/10/11/12 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 gscfq@t-online.de 2022-02-08 9:04 ` [Bug fortran/104430] " rguenth at gcc dot gnu.org 2022-02-24 10:44 ` [Bug fortran/104430] [9/10/11/12 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 since r9-3522-gd0477233215e37de marxin at gcc dot gnu.org 2022-03-07 21:12 ` cvs-commit at gcc dot gnu.org 2022-03-19 7:49 ` cvs-commit at gcc dot gnu.org 2022-05-27 9:47 ` [Bug fortran/104430] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-27 19:55 ` [Bug fortran/104430] [10 " anlauf at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2022-08-26 10:59 ` redi at gcc dot gnu.org [this message] 2022-08-26 11:04 ` redi at gcc dot gnu.org 2023-06-02 8:52 ` 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-104430-4-vnGRnmTtpt@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).