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/58857] [OOP] CLASS wrongly rejected in BLOCK DATA Date: Sat, 14 Dec 2013 17:06:00 -0000 [thread overview] Message-ID: <bug-58857-4-JgQjyptagz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58857-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58857 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2013-12-14 CC| |janus at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from janus at gcc dot gnu.org --- The whole idea of using CLASS(*) with BLOCK DATA is rather sick if you ask me ;) Anyway, here is a draft patch which helps to allow this bestiality (not regtested): Index: gcc/fortran/class.c =================================================================== --- gcc/fortran/class.c (revision 205983) +++ gcc/fortran/class.c (working copy) @@ -644,7 +644,7 @@ gfc_build_class_symbol (gfc_typespec *ts, symbol_a if (!gfc_add_component (fclass, "_vptr", &c)) return false; c->ts.type = BT_DERIVED; - if (delayed_vtab + if (delayed_vtab || ts->u.derived->attr.unlimited_polymorphic || (ts->u.derived->f2k_derived && ts->u.derived->f2k_derived->finalizers)) c->ts.u.derived = NULL;
prev parent reply other threads:[~2013-12-14 17:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-23 21:31 [Bug fortran/58857] New: " burnus at gcc dot gnu.org 2013-10-29 23:06 ` [Bug fortran/58857] " burnus at gcc dot gnu.org 2013-12-14 17:06 ` janus at gcc dot gnu.org [this message]
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-58857-4-JgQjyptagz@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).