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/95504] ICE in transfer_array_component, at fortran/trans-io.c:2167 Date: Wed, 03 Jun 2020 15:48:01 +0000 [thread overview] Message-ID: <bug-95504-4-qYrDL8XRtS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95504-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95504 G. Steinmetz <gscfq@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-invalid-code --- Comment #1 from G. Steinmetz <gscfq@t-online.de> --- With a non-parameterized type instead : $ cat zz1.f90 program p type t integer :: n integer, pointer :: a(:) end type type(t) :: z print *, z end $ gfortran-11-20200531 -c zz1.f90 zz1.f90:7:13: 7 | print *, z | 1 Error: Data transfer element at (1) cannot have POINTER components unless it is processed by a defined input/output procedure
next prev parent reply other threads:[~2020-06-03 15:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-03 15:47 [Bug fortran/95504] New: " gscfq@t-online.de 2020-06-03 15:48 ` gscfq@t-online.de [this message] 2020-06-03 18:43 ` [Bug fortran/95504] [PDT] " anlauf at gcc dot gnu.org 2023-06-30 8:12 ` pault 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-95504-4-qYrDL8XRtS@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).