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/100971] New: ICE: Bad IO basetype (7) Date: Tue, 08 Jun 2021 17:13:33 +0000 [thread overview] Message-ID: <bug-100971-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100971 Bug ID: 100971 Summary: ICE: Bad IO basetype (7) 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: --- This invalid code z1 affects versions down to at least r5. For reference, the case z0 is already rejected. $ cat z0.f90 program p type t end type class(t), allocatable :: a print *, a end $ cat z1.f90 program p type t end type class(t), allocatable :: a print *, [a] end $ gfortran-12-20210606 -c z0.f90 z0.f90:5:13: 5 | print *, a | 1 Error: Data transfer element at (1) cannot be polymorphic unless it is processed by a defined input/output procedure $ gfortran-12-20210606 -c z1.f90 f951: internal compiler error: Bad IO basetype (7) 0x6ea049 gfc_report_diagnostic ../../gcc/fortran/error.c:782 0x6eb76a gfc_internal_error(char const*, ...) ../../gcc/fortran/error.c:1402 0x7f9e09 transfer_expr ../../gcc/fortran/trans-io.c:2507 0x7fd430 gfc_trans_transfer(gfc_code*) ../../gcc/fortran/trans-io.c:2661 0x79e6c7 trans_code ../../gcc/fortran/trans.c:2138 0x7faefe build_dt ../../gcc/fortran/trans-io.c:2026 0x79e6a7 trans_code ../../gcc/fortran/trans.c:2110 0x7c4bc4 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.c:6893 0x74b3f6 translate_all_program_units ../../gcc/fortran/parse.c:6461 0x74b3f6 gfc_parse_file() ../../gcc/fortran/parse.c:6730 0x79772f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:212
next reply other threads:[~2021-06-08 17:13 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-08 17:13 gscfq@t-online.de [this message] 2021-06-20 20:35 ` [Bug fortran/100971] " jvdelisle2 at gmail dot com 2021-06-21 19:04 ` dominiq at lps dot ens.fr 2022-10-06 20:58 ` anlauf at gcc dot gnu.org 2022-10-09 18:57 ` anlauf at gcc dot gnu.org 2022-10-14 20:17 ` cvs-commit at gcc dot gnu.org 2022-10-14 20:21 ` 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-100971-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).