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/59414] [4.8/4.9 Regression] [OOP] ICE in in gfc_conv_expr_descriptor on ALLOCATE inside SELECT TYPE
Date: Tue, 28 Jan 2014 20:11:00 -0000 [thread overview]
Message-ID: <bug-59414-4-sGYgvY6IN6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59414-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59414
--- Comment #16 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Tue Jan 28 20:10:22 2014
New Revision: 207204
URL: http://gcc.gnu.org/viewcvs?rev=207204&root=gcc&view=rev
Log:
2014-01-28 Paul Thomas <pault@gcc.gnu.org>
PR fortran/59414
* trans-stmt.c (gfc_trans_allocate): Before the pointer
assignment to transfer the source _vptr to a class allocate
expression, the final class reference should be exposed. The
tail that includes the _data and array references is stored.
This reduced expression is transferred to 'lhs' and the _vptr
added. Then the tail is restored to the allocate expression.
2014-01-28 Paul Thomas <pault@gcc.gnu.org>
PR fortran/59414
* gfortran.dg/allocate_class_3.f90 : New test
Added:
trunk/gcc/testsuite/gfortran.dg/allocate_class_3.f90
trunk/gcc/testsuite/gfortran.dg/elemental_by_value_1.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-stmt.c
trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2014-01-28 20:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 18:53 [Bug fortran/59414] New: Class array pointers: compile error on valid code (Different ranks in pointer assignment) antony at cosmologist dot info
2013-12-07 11:12 ` [Bug fortran/59414] [OOP] " janus at gcc dot gnu.org
2013-12-07 11:56 ` janus at gcc dot gnu.org
2013-12-07 12:33 ` antony at cosmologist dot info
2013-12-07 12:46 ` janus at gcc dot gnu.org
2013-12-07 14:04 ` dominiq at lps dot ens.fr
2013-12-07 14:26 ` janus at gcc dot gnu.org
2013-12-07 15:13 ` janus at gcc dot gnu.org
2013-12-07 16:59 ` kargl at gcc dot gnu.org
2013-12-07 19:27 ` janus at gcc dot gnu.org
2013-12-07 19:30 ` janus at gcc dot gnu.org
2013-12-19 15:21 ` [Bug fortran/59414] [4.8/4.9 Regression] [OOP] ICE in in gfc_conv_expr_descriptor on ALLOCATE inside SELECT TYPE rguenth at gcc dot gnu.org
2014-01-19 12:34 ` pault at gcc dot gnu.org
2014-01-19 21:06 ` pault at gcc dot gnu.org
2014-01-26 14:31 ` mikael at gcc dot gnu.org
2014-01-26 17:41 ` paul.richard.thomas at gmail dot com
2014-01-28 20:11 ` pault at gcc dot gnu.org [this message]
2014-01-28 20:18 ` [Bug fortran/59414] [4.8 " pault at gcc dot gnu.org
2014-02-01 22:32 ` pault at gcc dot gnu.org
2014-02-01 22:34 ` pault 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-59414-4-sGYgvY6IN6@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).