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/57590] [OOP] wrong code with class variables of different shapes
Date: Tue, 20 Aug 2013 15:28:00 -0000	[thread overview]
Message-ID: <bug-57590-4-TdYILm1G7u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57590-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57590

--- Comment #11 from janus at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #6)
> The two above need some adjustements at translation stage, which defeats the
> purpose of generating the class container using front-end structures only.
> Thus, I'm more in favor of (3):
>  (3) Don't use gfc_build_class_symbol, or delay it as much as possible until 
>      code generation.

Yes, that might indeed be beneficial. I have already thought about this on a
few occasions.

It would be a larger project for sure, but it could simplify many things. Of
course there may also be some pitfalls lurking. I think the cleanest approach
would be to keep all the polymorphics as plain BT_CLASS variables (with all the
attributes as they are) in the front end and during resolution, and only
generate the class containers and vtabs at translation stage.


      parent reply	other threads:[~2013-08-20 15:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 18:47 [Bug fortran/57590] New: [OOP] class containers are recycled between symbols more than they should be mikael at gcc dot gnu.org
2013-06-27  9:24 ` [Bug fortran/57590] " dominiq at lps dot ens.fr
2013-08-20 12:20 ` [Bug fortran/57590] [OOP] wrong code with class variables of different shapes janus at gcc dot gnu.org
2013-08-20 13:07 ` janus at gcc dot gnu.org
2013-08-20 13:19 ` janus at gcc dot gnu.org
2013-08-20 13:48 ` mikael at gcc dot gnu.org
2013-08-20 13:51 ` mikael at gcc dot gnu.org
2013-08-20 14:34 ` janus at gcc dot gnu.org
2013-08-20 15:06 ` janus at gcc dot gnu.org
2013-08-20 15:28 ` 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-57590-4-TdYILm1G7u@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: link
Be 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).