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/104626] New: ICE in gfc_format_decoder, at fortran/error.cc:1071 Date: Mon, 21 Feb 2022 21:33:42 +0000 [thread overview] Message-ID: <bug-104626-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104626 Bug ID: 104626 Summary: ICE in gfc_format_decoder, at fortran/error.cc:1071 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: --- Affects versions down to at least r5 : $ cat z1.f90 program p procedure(g), save :: f procedure(g), save :: f contains subroutine g end end $ cat z2.f90 program p procedure(g), save :: f contains subroutine g end end $ gfortran-12-20220220 -c z2.f90 z2.f90:2:26: 2 | procedure(g), save :: f | 1 Error: PROCEDURE attribute conflicts with SAVE attribute in 'f' at (1) $ gfortran-12-20220220 -c z1.f90 0xe7133f crash_signal ../../gcc/toplev.cc:322 0x72db98 gfc_format_decoder ../../gcc/fortran/error.cc:1071 0x1e7e570 pp_format(pretty_printer*, text_info*) ../../gcc/pretty-print.cc:1475 0x1e60195 diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*) ../../gcc/diagnostic.cc:1384 0x72da91 gfc_report_diagnostic ../../gcc/fortran/error.cc:883 0x72da91 gfc_warning ../../gcc/fortran/error.cc:916 0x72ebc1 gfc_notify_std(int, char const*, ...) ../../gcc/fortran/error.cc:1039 0x7ce70c gfc_add_save(symbol_attribute*, save_state, char const*, locus*) ../../gcc/fortran/symbol.cc:1314 0x7d0070 gfc_copy_attr(symbol_attribute*, symbol_attribute*, locus*) ../../gcc/fortran/symbol.cc:2093 0x721a5b match_procedure_decl ../../gcc/fortran/decl.cc:7064 0x721a5b gfc_match_procedure() ../../gcc/fortran/decl.cc:7365 0x787501 match_word ../../gcc/fortran/parse.cc:67 0x78d0a6 decode_statement ../../gcc/fortran/parse.cc:544 0x78d46a next_free ../../gcc/fortran/parse.cc:1397 0x78d46a next_statement ../../gcc/fortran/parse.cc:1629 0x78e9fb parse_spec ../../gcc/fortran/parse.cc:4168 0x791b4c parse_progunit ../../gcc/fortran/parse.cc:6192 0x793211 gfc_parse_file() ../../gcc/fortran/parse.cc:6737 0x7e154f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:216
next reply other threads:[~2022-02-21 21:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-21 21:33 gscfq@t-online.de [this message] 2022-02-21 23:17 ` [Bug fortran/104626] " kargl at gcc dot gnu.org 2023-05-29 23:57 ` kargl at gcc dot gnu.org 2023-10-13 20:12 ` 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-104626-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).