public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olchansk at panix dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/15181] New: gfc_conv_component_ref: Assertion `c->backend_decl' failed Date: Tue, 27 Apr 2004 22:41:00 -0000 [thread overview] Message-ID: <20040427221144.15181.olchansk@panix.com> (raw) cvs-head tree-ssa gfortran (gcc version 3.5-tree-ssa 20040423 (merged 20040414)) fails to compile this code. It works fine with Absoft and ICC. module foo implicit none type:: wire_type integer iwire end type wire_type type:: tdc_type integer iabc type(wire_type), pointer:: wireP end type tdc_type type(tdc_type):: pctdc(100) contains subroutine bar integer ii integer itdc !! following line causes ICE: !! f951: ../../gcc/gcc/fortran/trans-expr.c:219: !! gfc_conv_component_ref: Assertion `c->backend_decl' failed. ii = PCtdc(iTDC)%WireP%iwire end subroutine bar end module foo [olchansk@dork gfortran_test]$ make test_gfc_conv_component_ref.o /triumfcs/trshare/olchansk/gcc-tree-ssa/install/bin/gfortran -x f95 -c -o test_gfc_conv_component_ref.o -O2 -g -Wall -Waliasing -Wline-truncation -Wsurprising -Wunused-labels -fPIC -ffixed-line-length-132 test_gfc_conv_component_ref.f90 f951: ../../gcc/gcc/fortran/trans-expr.c:219: gfc_conv_component_ref: Assertion `c->backend_decl' failed. test_gfc_conv_component_ref.f90: In function `bar': test_gfc_conv_component_ref.f90:25: internal compiler error: Aborted Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. make: *** [test_gfc_conv_component_ref.o] Error 1 K.O. -- Summary: gfc_conv_component_ref: Assertion `c->backend_decl' failed Product: gcc Version: tree-ssa Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: olchansk at panix dot com CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15181
next reply other threads:[~2004-04-27 22:12 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-27 22:41 olchansk at panix dot com [this message] 2004-04-27 22:44 ` [Bug fortran/15181] [gfortran] " pinskia at gcc dot gnu dot org 2004-05-27 3:10 ` pinskia at gcc dot gnu dot org 2004-06-13 9:16 ` pinskia at gcc dot gnu dot org 2004-07-12 2:30 ` [Bug fortran/15181] " olchansk at panix dot com 2004-09-26 16:16 ` tobi at gcc dot gnu dot org 2004-09-30 21:57 ` pinskia at gcc dot gnu dot org 2004-10-09 22:29 ` olchansk at panix dot com 2004-10-15 19:59 ` dr dot johan at gmail dot com 2004-10-15 20:17 ` tobi at gcc dot gnu dot org 2004-11-11 19:11 ` pinskia at gcc dot gnu dot org 2005-02-16 9:42 ` pinskia at gcc dot gnu dot 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=20040427221144.15181.olchansk@panix.com \ --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).