public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/46201] [F03] ICE on procedure pointer component call Date: Wed, 27 Oct 2010 22:03:00 -0000 [thread overview] Message-ID: <20101027220300.LXMWAqabQ-SPgsE4Cx4PcjBX7in-gqlKlwhBRCV--Eg@z> (raw) In-Reply-To: <bug-46201-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46201 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2010.10.27 22:03:01 Summary|ICE using procedure |[F03] ICE on procedure |pointer... |pointer component call Ever Confirmed|0 |1 --- Comment #2 from janus at gcc dot gnu.org 2010-10-27 22:03:01 UTC --- Here is a slightly reduced/modified test case: implicit none abstract interface character function name_func (ivar) result (res) integer, intent(in) :: ivar end function end interface type var_type procedure(name_func), nopass, pointer :: name end type type(var_type), dimension(1) :: vars print *,vars(1)%name(1) end
next prev parent reply other threads:[~2010-10-27 22:03 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-27 20:50 [Bug fortran/46201] New: ICE using procedure pointer sjbespa at comcast dot net 2010-10-27 21:48 ` [Bug fortran/46201] " burnus at gcc dot gnu.org 2010-10-27 22:03 ` janus at gcc dot gnu.org [this message] 2010-12-13 16:57 ` [Bug fortran/46201] [F03] ICE on procedure pointer component call janus at gcc dot gnu.org 2010-12-13 17:39 ` janus at gcc dot gnu.org 2010-12-13 19:18 ` janus at gcc dot gnu.org 2010-12-13 19:22 ` janus at gcc dot gnu.org 2010-12-13 21:39 ` dominiq at lps dot ens.fr 2010-12-13 21:51 ` janus at gcc dot gnu.org 2010-12-13 22:13 ` dominiq at lps dot ens.fr
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=20101027220300.LXMWAqabQ-SPgsE4Cx4PcjBX7in-gqlKlwhBRCV--Eg@z \ --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).