public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "t56xjcu6dh at snkmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65766] gFortran Compiler SEGFAULTING on compiling simple program
Date: Tue, 28 Jul 2015 08:38:00 -0000	[thread overview]
Message-ID: <bug-65766-4-2o65QS26Uv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65766-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65766

--- Comment #3 from Louis Krupp <t56xjcu6dh at snkmail dot com> ---
Created attachment 36080
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36080&action=edit
Proposed patch

The problem is with substrings of allocatable string components of derived
types.  The code seems to be trying to get the string length from typespec of
the derived type variable instead of from the component.

The attached patch gets the component typespec from the reference chain.

I don't understand the code well enough to have a lot of confidence in this
patch, but it seems like a step in the right direction.


  parent reply	other threads:[~2015-07-28  8:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15  0:19 [Bug fortran/65766] New: " giorgianb at gmail dot com
2015-04-15  1:52 ` [Bug fortran/65766] " jvdelisle at gcc dot gnu.org
2015-07-28  8:26 ` t56xjcu6dh at snkmail dot com
2015-07-28  8:38 ` t56xjcu6dh at snkmail dot com [this message]
2015-07-30 12:11 ` dominiq at lps dot ens.fr
2015-09-10 10:00 ` dominiq at lps dot ens.fr
2015-09-10 10:01 ` dominiq at lps dot ens.fr
2015-09-10 10:04 ` dominiq at lps dot ens.fr
2015-10-06 23:47 ` lkrupp at gcc dot gnu.org
2015-10-07  0:14 ` lkrupp at gcc dot gnu.org
2015-10-07  7:47 ` dominiq at lps dot ens.fr
2015-10-07  9:30 ` louis.krupp at zoho dot com

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-65766-4-2o65QS26Uv@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).