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/107074] New: ICE: Bad IO basetype (8) Date: Wed, 28 Sep 2022 17:34:10 +0000 [thread overview] Message-ID: <bug-107074-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107074 Bug ID: 107074 Summary: ICE: Bad IO basetype (8) Product: gcc Version: 13.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 : (a is a procedure/function) $ cat z1.f90 program p implicit none integer :: a print *, a(1) print *, merge(a, a, .true.) end $ cat z2.f90 program p implicit none integer :: a print *, a() print *, merge(a, a, .true.) end $ gfortran-13-20220925 -c z1.f90 f951: internal compiler error: Bad IO basetype (8) 0x7f4459 gfc_report_diagnostic ../../gcc/fortran/error.cc:883 0x7f5fd7 gfc_internal_error(char const*, ...) ../../gcc/fortran/error.cc:1503 0x9308f6 transfer_expr ../../gcc/fortran/trans-io.cc:2532 0x934b3e gfc_trans_transfer(gfc_code*) ../../gcc/fortran/trans-io.cc:2686 0x8b1cd7 trans_code ../../gcc/fortran/trans.cc:2170 0x9323d2 build_dt ../../gcc/fortran/trans-io.cc:2051 0x8b1cf7 trans_code ../../gcc/fortran/trans.cc:2142 0x8e95d9 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.cc:7655 0x85afae translate_all_program_units ../../gcc/fortran/parse.cc:6671 0x85afae gfc_parse_file() ../../gcc/fortran/parse.cc:6977 0x8a925f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:229
next reply other threads:[~2022-09-28 17:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-28 17:34 gscfq@t-online.de [this message] 2022-09-28 18:53 ` [Bug fortran/107074] " anlauf at gcc dot gnu.org 2022-09-28 19:10 ` anlauf at gcc dot gnu.org 2022-10-03 20:31 ` anlauf at gcc dot gnu.org 2022-10-04 19:35 ` 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-107074-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).