public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/47463] [OOP] ICE in gfc_add_component_ref Date: Tue, 25 Jan 2011 20:33:00 -0000 [thread overview] Message-ID: <bug-47463-4-whL4rglKHv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47463-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47463 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org, | |janus at gcc dot gnu.org Summary|ICE in |[OOP] ICE in |gfc_add_component_ref |gfc_add_component_ref --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-01-25 19:53:04 UTC --- 4.5 fails with: use hydro_recon 1 Internal Error at (1): mio_component_ref(): Component not found Thus, it is not a regression. * * * Compiling with Crayftn 7.2.4 shows the error: call this%init(st, gr) ^ ftn-389 crayftn: ERROR INIT_PARAMS, File = hydro_flow.f90, Line = 55, Column = 14 No specific match can be found for the generic subprogram call "INIT". * * * Regarding GCC 4.6: The ICE occurs in gfc_add_component_ref for e being the EXPR_FUNCTION "this->_vptr" where "_vptr" is e->ref->u.c.component->name and e->ref->next == NULL. Also e->value.function == {actual = 0x0, name = 0x0, isym = 0x0, esym = 0x0}. The caller is resolve_typebound_subroutine where code->op == EXEC_ASSIGN_CALL; the call is: gfc_add_component_ref (code->expr1, name); with "name" == assign and the expression as shown above. Somewhat reduced test case: module hydro_state type :: state_t contains procedure :: assign generic :: assignment(=) => assign end type state_t contains subroutine assign (this, that) class(state_t), intent(inout) :: this class(state_t), intent(in) :: that end subroutine assign end module hydro_state module hydro_flow use hydro_state type :: flow_t class(state_t), allocatable :: st end type flow_t contains subroutine init_comps (this, st) class(flow_t), intent(out) :: this class(state_t), intent(in) :: st allocate(state_t :: this%st) this%st = st end subroutine init_comps end module hydro_flow
next prev parent reply other threads:[~2011-01-25 19:53 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-25 19:33 [Bug fortran/47463] New: " townsend at astro dot wisc.edu 2011-01-25 20:33 ` burnus at gcc dot gnu.org [this message] 2011-01-25 20:53 ` [Bug fortran/47463] [OOP] " mikael at gcc dot gnu.org 2011-01-27 5:33 ` townsend at astro dot wisc.edu 2011-01-30 16:01 ` janus at gcc dot gnu.org 2011-01-31 10:48 ` janus at gcc dot gnu.org 2011-01-31 12:08 ` burnus at gcc dot gnu.org 2011-01-31 15:13 ` janus at gcc dot gnu.org 2011-01-31 18:46 ` janus at gcc dot gnu.org 2011-01-31 21:53 ` burnus at gcc dot gnu.org 2011-02-02 18:25 ` dnovillo at gcc dot gnu.org 2011-02-09 18:11 ` janus at gcc dot gnu.org 2011-02-09 18:58 ` burnus at gcc dot gnu.org 2011-02-09 20:24 ` janus at gcc dot gnu.org 2011-02-09 20:35 ` janus at gcc dot gnu.org 2011-02-09 20:49 ` janus at gcc dot gnu.org 2011-02-09 21:10 ` burnus at gcc dot gnu.org 2011-02-10 6:25 ` paul.richard.thomas at gmail dot com
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-47463-4-whL4rglKHv@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).