public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danlnagle at me dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51605] internal compiler error gfc_trans_block_construct, at fortran/trans-stmt.c:984 Date: Sun, 18 Dec 2011 13:55:00 -0000 [thread overview] Message-ID: <bug-51605-4-jL9CUfpClw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51605-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51605 --- Comment #5 from Dan Nagle <danlnagle at me dot com> 2011-12-18 13:13:48 UTC --- Citations from 10-007r1.pdf [185:17-18] says the polymorphic symbol_ptr takes the type of the type guard within the type guard. [171:7-8] says the associating entity loses the pointer attribute but keeps the target attribute. (It has the target attribute because it was a pointer outside the type guard.) Therefore I believe it's conforming to point to the associating entity with a typed pointer. (integer_ptr => symbol_ptr) My analysis could be faulty. I'm using the gfortran I'm using because it had a Mac installer. I thought 4.6.2 was fairly recent. This is all new stuff and I'm learning it myself and getting surprised here and there. Thanks for your efforts.
next prev parent reply other threads:[~2011-12-18 13:14 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-17 22:46 [Bug fortran/51605] New: " danlnagle at me dot com 2011-12-17 23:26 ` [Bug fortran/51605] " danlnagle at me dot com 2011-12-17 23:48 ` dominiq at lps dot ens.fr 2011-12-18 9:24 ` kargl at gcc dot gnu.org 2011-12-18 10:08 ` burnus at gcc dot gnu.org 2011-12-18 13:55 ` danlnagle at me dot com [this message] 2011-12-18 14:15 ` burnus at gcc dot gnu.org 2011-12-18 16:57 ` sgk at troutmask dot apl.washington.edu 2011-12-19 11:52 ` burnus at gcc dot gnu.org 2011-12-19 13:19 ` burnus at gcc dot gnu.org 2011-12-19 15:32 ` burnus at gcc dot gnu.org 2011-12-19 15:54 ` danlnagle at me dot com 2011-12-19 18:56 ` burnus at gcc dot gnu.org 2011-12-19 20:26 ` burnus at gcc dot gnu.org 2011-12-19 20:30 ` burnus at gcc dot gnu.org 2013-12-14 20:15 ` dominiq at lps dot ens.fr 2013-12-14 22:25 ` janus at gcc dot gnu.org 2023-03-06 17:18 ` anlauf 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-51605-4-jL9CUfpClw@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).