public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51995] [OOP] Polymorphic class fails at runtime Date: Wed, 25 Jan 2012 13:34:00 -0000 [thread overview] Message-ID: <bug-51995-4-GvxkUIJYX9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51995-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51995 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |burnus at gcc dot gnu.org |gnu.org | --- Comment #8 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-25 13:29:48 UTC --- (In reply to comment #4) > I tested the program on i686 GNU/Linux running on Ubuntu-Maverick using gcc > version 4.7.0 20120118 (experimental) (GCC). > > So it is definitely a bug in gfortran. Do you have any work-around? Unfortunately, I am not aware of a workaround. I have to admit that I have not fully understood why fclass->f2k_derived gets often but not always set. However, the following patch works. Thus, you could either apply it and build your own GCC, or you wait a day after the committal and get a nightly build at http://gcc.gnu.org/wiki/GFortranBinaries - or you convince Matthias to do a new Ubuntu build. (In reply to comment #7) > There, the problem is that one has: > sym = sym->ts.u.derived; > if (sym->f2k_derived) Actually, f2k_derived should also get set for the class container. Better patch (read: actually working) patch: --- a/gcc/fortran/class.c +++ b/gcc/fortran/class.c @@ -421,6 +421,8 @@ gfc_build_class_symbol (gfc_typespec *ts, symbol_attribute *attr, c->attr.access = ACCESS_PRIVATE; c->attr.pointer = 1; } + else if (!fclass->f2k_derived) + fclass->f2k_derived = fclass->components->ts.u.derived->f2k_derived; /* Since the extension field is 8 bit wide, we can only have up to 255 extension levels. */
next prev parent reply other threads:[~2012-01-25 13:30 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-25 10:36 [Bug fortran/51995] New: " jilfa12 at yahoo dot com 2012-01-25 11:12 ` [Bug fortran/51995] " dominiq at lps dot ens.fr 2012-01-25 11:15 ` burnus at gcc dot gnu.org 2012-01-25 11:18 ` burnus at gcc dot gnu.org 2012-01-25 11:39 ` jilfa12 at yahoo dot com 2012-01-25 11:42 ` [Bug fortran/51995] [OOP] " burnus at gcc dot gnu.org 2012-01-25 11:43 ` jilfa12 at yahoo dot com 2012-01-25 13:10 ` burnus at gcc dot gnu.org 2012-01-25 13:34 ` burnus at gcc dot gnu.org [this message] 2012-01-25 14:09 ` jilfa12 at yahoo dot com 2012-01-25 18:19 ` burnus at gcc dot gnu.org 2012-01-25 18:26 ` burnus at gcc dot gnu.org 2012-01-25 19:25 ` dominiq at lps dot ens.fr 2012-01-25 20:34 ` dominiq at lps dot ens.fr 2012-01-25 23:18 ` 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-51995-4-GvxkUIJYX9@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).