public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/60255] [OOP] Deferred character length variable at (1) cannot yet be associated with unlimited polymorphic entities Date: Sun, 18 Jan 2015 22:02:00 -0000 [thread overview] Message-ID: <bug-60255-4-cGLJOI8hyW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60255-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60255 --- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> --- Author: pault Date: Sun Jan 18 22:01:29 2015 New Revision: 219827 URL: https://gcc.gnu.org/viewcvs?rev=219827&root=gcc&view=rev Log: 2015-01-18 Andre Vehreschild <vehre@gmx.de> Janus Weil <janus@gcc.gnu.org> PR fortran/60255 * class.c (gfc_get_len_component): New. (gfc_build_class_symbol): Add _len component to unlimited polymorphic entities. (find_intrinsic_vtab): Removed emitting of error message. * gfortran.h: Added prototype for gfc_get_len_component. * simplify.c (gfc_simplify_len): Use _len component where available. * trans-expr.c (gfc_class_len_get): New. (gfc_conv_intrinsic_to_class): Add handling for deferred character arrays. (gfc_conv_structure): Treat _len component correctly. (gfc_conv_expr): Prevent bind_c handling when not required. (gfc_trans_pointer_assignment): Propagate _len component. * trans-stmt.c (class_has_len_component): New. (trans_associate_var): _len component treatment for associate context. (gfc_trans_allocate): Same as for trans_associate_var() * trans.h: Added prototype for gfc_class_len_get. 2015-01-18 Andre Vehreschild <vehre@gmx.de> PR fortran/60255 * gfortran.dg/unlimited_polymorphic_2.f03: Removed error. * gfortran.dg/unlimited_polymorphic_20.f03: New test. 2015-01-18 Paul Thomas <pault@gcc.gnu.org> PR fortran/64578 * gfortran.dg/unlimited_polymorphic_21.f90: New test Added: trunk/gcc/testsuite/gfortran.dg/unlimited_polymorphic_20.f90 trunk/gcc/testsuite/gfortran.dg/unlimited_polymorphic_21.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/class.c trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/simplify.c trunk/gcc/fortran/trans-expr.c trunk/gcc/fortran/trans-stmt.c trunk/gcc/fortran/trans.h trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/unlimited_polymorphic_2.f03
next prev parent reply other threads:[~2015-01-18 22:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-18 0:03 [Bug fortran/60255] New: " antony at cosmologist dot info 2014-02-18 2:00 ` [Bug fortran/60255] " kargl at gcc dot gnu.org 2014-02-18 9:09 ` janus at gcc dot gnu.org 2014-02-18 14:20 ` janus at gcc dot gnu.org 2014-02-19 10:06 ` dominiq at lps dot ens.fr 2014-02-19 12:08 ` janus at gcc dot gnu.org 2014-02-27 14:30 ` antony at cosmologist dot info 2015-01-18 22:02 ` pault at gcc dot gnu.org [this message] 2015-01-23 10:56 ` [Bug fortran/60255] [OOP] " vehre at gmx dot de 2015-03-23 12:57 ` vehre 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-60255-4-cGLJOI8hyW@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).