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/56385] [OOP] ICE with allocatable function result in a procedure-pointer component Date: Mon, 18 Feb 2013 22:15:00 -0000 [thread overview] Message-ID: <bug-56385-4-28OP2aY5w5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56385-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56385 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-invalid-code Status|UNCONFIRMED |NEW Last reconfirmed| |2013-02-18 CC| |janus at gcc dot gnu.org Summary|ICE with allocatable |[OOP] ICE with allocatable |function result in a |function result in a |type-bound procedure |procedure-pointer component Ever Confirmed|0 |1 --- Comment #1 from janus at gcc dot gnu.org 2013-02-18 22:14:55 UTC --- ICE confirmed with 4.6, 4.7 and trunk. Reduced test case: module VolumeSources implicit none type :: TGeometricShape end type type :: TVolumeSourceBody class(TGeometricShape), allocatable :: GeometricShape procedure(scalar_flux_interface), pointer :: get_scalar_flux end type TVolumeSourceBody abstract interface function scalar_flux_interface(self) result(res) import real, allocatable :: res(:) class(TVolumeSourceBody), intent(in) :: self end function end interface end module Note: 'get_scalar_flux' is actually not a type-bound procedure, but a procedure-pointer component.
next prev parent reply other threads:[~2013-02-18 22:15 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-18 21:54 [Bug fortran/56385] New: ICE with allocatable function result in a type-bound procedure vladimir.fuka at gmail dot com 2013-02-18 22:15 ` janus at gcc dot gnu.org [this message] 2013-02-18 22:25 ` [Bug fortran/56385] [4.6/4.7/4.8 Regression] [OOP] ICE with allocatable function result in a procedure-pointer component dominiq at lps dot ens.fr 2013-02-19 15:21 ` janus at gcc dot gnu.org 2013-02-21 12:27 ` janus at gcc dot gnu.org 2013-02-22 19:48 ` janus at gcc dot gnu.org 2013-02-23 14:41 ` janus at gcc dot gnu.org 2013-02-23 14:42 ` janus 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-56385-4-28OP2aY5w5@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).