public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alexandre.poux at coria dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/111321] New: Segmentation fault with associate construct Date: Thu, 07 Sep 2023 07:53:57 +0000 [thread overview] Message-ID: <bug-111321-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111321 Bug ID: 111321 Summary: Segmentation fault with associate construct Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: alexandre.poux at coria dot fr Target Milestone: --- The following program triggers a segmentation fault when compiling ```fortran program buggy implicit none double precision, dimension(1) :: array integer :: i associate (assoc => array) assoc(1) = 1.5 assoc = assoc*2 end associate contains end program buggy ``` ``` #> gfortran bug.f90 f951: internal compiler error: Segmentation fault 0x1a0e9c4 internal_error(char const*, ...) ???:0 0x77d375 gfc_expression_rank(gfc_expr*) ???:0 0x7392fc gfc_match_expr(gfc_expr**) ???:0 0x7397a8 gfc_match(char const*, ...) ???:0 0x739f59 gfc_match_assignment() ???:0 0x793a70 gfc_parse_file() ???:0 ``` I'm using the latest version of gfortran from the archlinux repository core/gcc-fortran 13.2.1-3
next reply other threads:[~2023-09-07 7:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-07 7:53 alexandre.poux at coria dot fr [this message] 2023-09-07 7:55 ` [Bug fortran/111321] " alexandre.poux at coria dot fr 2023-09-07 13:04 ` kopper at iag dot uni-stuttgart.de 2023-09-07 16:04 ` 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-111321-4@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).