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/103506] New: [10/11/12 Regression] ICE in gfc_free_namespace, at fortran/symbol.c:4039 Date: Tue, 30 Nov 2021 18:49:09 +0000 [thread overview] Message-ID: <bug-103506-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506 Bug ID: 103506 Summary: [10/11/12 Regression] ICE in gfc_free_namespace, at fortran/symbol.c:4039 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started between 20190818 and 20190825 : $ cat z1.f90 module m stop end program p call m end $ cat z2.f90 module m continue end program p call m end $ cat z3.f90 module m do end program p call m end $ gfortran-12-20211128 -c z1.f90 z1.f90:2:4: 2 | stop | 1 Error: Unexpected STOP statement in MODULE at (1) z1.f90:5:6: 1 | module m | 2 ...... 5 | call m | 1 Error: Global name 'm' at (1) is already being used as a MODULE at (2) f951: internal compiler error: in gfc_free_namespace, at fortran/symbol.c:4039 0x87bf15 gfc_free_namespace(gfc_namespace*&) ../../gcc/fortran/symbol.c:4039 0x87c459 gfc_symbol_done_2() ../../gcc/fortran/symbol.c:4105 0x8140f8 gfc_done_2() ../../gcc/fortran/misc.c:382 0x83152a clean_up_modules ../../gcc/fortran/parse.c:6596 0x8314ec clean_up_modules ../../gcc/fortran/parse.c:6586 0x83d9d1 translate_all_program_units ../../gcc/fortran/parse.c:6661 0x83d9d1 gfc_parse_file() ../../gcc/fortran/parse.c:6925 0x88b37f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:216
next reply other threads:[~2021-11-30 18:49 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-30 18:49 gscfq@t-online.de [this message] 2021-12-01 7:17 ` [Bug fortran/103506] " rguenth at gcc dot gnu.org 2021-12-01 9:28 ` [Bug fortran/103506] [10/11/12 Regression] ICE in gfc_free_namespace, at fortran/symbol.c:4039 since r10-2798-ge68a35ae4a65d2b3 marxin at gcc dot gnu.org 2021-12-22 23:52 ` kargl at gcc dot gnu.org 2022-06-28 10:47 ` [Bug fortran/103506] [10/11/12/13 " jakub at gcc dot gnu.org 2022-06-28 14:59 ` kargl at gcc dot gnu.org 2023-01-26 2:56 ` jvdelisle at gcc dot gnu.org 2023-01-26 18:29 ` sgk at troutmask dot apl.washington.edu 2023-01-27 2:06 ` jvdelisle at gcc dot gnu.org 2023-01-27 2:11 ` jvdelisle at gcc dot gnu.org 2023-01-27 2:14 ` jvdelisle at gcc dot gnu.org 2023-01-27 17:28 ` sgk at troutmask dot apl.washington.edu 2023-01-27 21:33 ` anlauf at gcc dot gnu.org 2023-01-27 21:52 ` tkoenig at gcc dot gnu.org 2023-01-28 0:59 ` jvdelisle at gcc dot gnu.org 2023-01-29 3:08 ` jvdelisle at gcc dot gnu.org 2023-01-29 19:10 ` cvs-commit at gcc dot gnu.org 2023-03-22 18:18 ` [Bug fortran/103506] [10/11/12 " anlauf at gcc dot gnu.org 2023-03-27 1:17 ` cvs-commit at gcc dot gnu.org 2023-07-07 10:41 ` [Bug fortran/103506] [11/12 " rguenth at gcc dot gnu.org 2023-07-08 19:43 ` [Bug fortran/103506] [11 " anlauf at gcc dot gnu.org 2023-08-05 23:44 ` cvs-commit at gcc dot gnu.org 2023-08-05 23:45 ` jvdelisle 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-103506-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).