public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/35810] [TR 15581 / F2003] Automatic reallocation on assignment to allocatable variables Date: Wed, 02 Feb 2011 18:23:00 -0000 [thread overview] Message-ID: <bug-35810-4-6usBdiuavq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-35810-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35810 --- Comment #20 from Diego Novillo <dnovillo at gcc dot gnu.org> 2011-02-02 18:04:44 UTC --- Author: dnovillo Date: Wed Feb 2 18:04:21 2011 New Revision: 169697 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169697 Log: 2011-01-30 Paul Thomas <pault@gcc.gnu.org> PR fortran/47523 * trans-expr.c (gfc_trans_assignment_1): If the rhs is an op expr and is assigned to a deferred character length scalar, make sure that the function is called before reallocation, so that the length is available. Include procedure pointer and procedure pointer component rhs as well. 2011-01-30 Paul Thomas <pault@gcc.gnu.org> PR fortran/47523 * trans-expr.c (gfc_trans_assignment_1): If the rhs is an op expr and is assigned to a deferred character length scalar, make sure that the function is called before reallocation, so that the length is available. Include procedure pointer and procedure pointer component rhs as well. PR fortran/45170 PR fortran/35810 PR fortran/47350 * gfortran.dg/allocatable_function_5.f90: New test not added by mistake on 2011-01-28. Added: branches/google/integration/gcc/testsuite/gfortran.dg/allocatable_function_5.f90 branches/google/integration/gcc/testsuite/gfortran.dg/realloc_on_assign_5.f03 Modified: branches/google/integration/gcc/fortran/ChangeLog branches/google/integration/gcc/fortran/trans-expr.c branches/google/integration/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2011-02-02 18:23 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-35810-4@http.gcc.gnu.org/bugzilla/> 2010-10-08 16:29 ` burnus at gcc dot gnu.org 2010-10-25 22:23 ` burnus at gcc dot gnu.org 2010-11-28 14:35 ` pault at gcc dot gnu.org 2010-12-30 12:18 ` janus at gcc dot gnu.org 2011-01-27 22:40 ` burnus at gcc dot gnu.org 2011-01-28 14:36 ` pault at gcc dot gnu.org 2011-01-28 15:16 ` burnus at gcc dot gnu.org 2011-01-28 15:18 ` burnus at gcc dot gnu.org 2011-01-28 15:48 ` burnus at gcc dot gnu.org 2011-01-30 18:19 ` pault at gcc dot gnu.org 2011-02-02 18:11 ` dnovillo at gcc dot gnu.org 2011-02-02 18:23 ` dnovillo at gcc dot gnu.org [this message] 2008-04-03 8:55 [Bug fortran/35810] New: [F2003] " burnus at gcc dot gnu dot org 2008-10-28 17:39 ` [Bug fortran/35810] [TR 15581 / F2003] " burnus at gcc dot gnu dot org 2008-11-10 19:47 ` pault at gcc dot gnu dot org 2008-11-28 13:30 ` mikael at gcc dot gnu dot org 2009-06-08 9:11 ` burnus at gcc dot gnu dot org 2009-08-07 19:27 ` kargl at gcc dot gnu dot org 2009-10-16 20:23 ` burnus at gcc dot gnu dot org 2010-03-31 18:05 ` burnus at gcc dot gnu dot org 2010-08-14 9:04 ` burnus at gcc dot gnu dot 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-35810-4-6usBdiuavq@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).