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/47565] [4.6 Regression][OOP] Segfault with TBP
Date: Tue, 01 Feb 2011 13:39:00 -0000	[thread overview]
Message-ID: <bug-47565-4-FKb3ZXy3Qi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47565-4@http.gcc.gnu.org/bugzilla/>

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
         AssignedTo|unassigned at gcc dot       |janus at gcc dot gnu.org
                   |gnu.org                     |

--- Comment #2 from janus at gcc dot gnu.org 2011-02-01 13:39:31 UTC ---
Here is the obvious fix:


Index: trans-expr.c
===================================================================
--- trans-expr.c        (revision 169470)
+++ trans-expr.c        (working copy)
@@ -4627,7 +4627,7 @@ gfc_conv_structure (gfc_se * se, gfc_expr * expr,
         components.  Although the latter have a default initializer
         of EXPR_NULL,... by default, the static nullify is not needed
         since this is done every time we come into scope.  */
-      if (!c->expr || cm->attr.allocatable)
+      if (!c->expr || (cm->attr.allocatable && cm->attr.flavor !=
FL_PROCEDURE))
         continue;

       if (strcmp (cm->name, "_size") == 0)



Will commit after regtesting.


  parent reply	other threads:[~2011-02-01 13:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01  8:49 [Bug fortran/47565] New: " burnus at gcc dot gnu.org
2011-02-01 13:01 ` [Bug fortran/47565] " janus at gcc dot gnu.org
2011-02-01 13:39 ` janus at gcc dot gnu.org [this message]
2011-02-01 15:00 ` janus at gcc dot gnu.org
2011-02-01 15:01 ` janus at gcc dot gnu.org
2011-02-02 18:33 ` dnovillo 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-47565-4-FKb3ZXy3Qi@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).