public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kaiserkarl31 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51383] New: arrays of extended types interact break associations with arrays Date: Thu, 01 Dec 2011 20:06:00 -0000 [thread overview] Message-ID: <bug-51383-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51383 Bug #: 51383 Summary: arrays of extended types interact break associations with arrays Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: kaiserkarl31@yahoo.com An ASSOCIATE block that associates a name with an array of derived types causes a compiler error. It is easily reproduced with the following short program: program extend type :: a integer :: i end type a type, extends (a) :: b integer :: j end type b type (a) :: x(2) type (b) :: y(2) associate (x1 => x, y1 => y) x1(1)%i = 1 ! Commenting out the following line will avoid the error y1(1)%i = 2 end associate end program extend In my version, I get the following error: ## start error message ## associate.f90:1.14: program extend 1 Internal Error at (1): find_array_spec(): Component not found ## end error message ## This example is trivial, of course (just use y instead of y1 and all is well), but if the association is something like associate (y1 => really_long%complicated(3)%variable(2)%array) it becomes more than a triviality.... As can be seen from the example above, this bug does not occur for "normal" derived types, only ones created with the EXTENDS key word.
next reply other threads:[~2011-12-01 20:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-01 20:06 kaiserkarl31 at yahoo dot com [this message] 2011-12-04 16:34 ` [Bug fortran/51383] [OOP] arrays of extended types break when associated burnus at gcc dot gnu.org 2011-12-04 16:35 ` burnus 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-51383-4@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).