public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65841] Seg fault on intrinsic assignment to allocatable derived type with allocatable component
Date: Wed, 22 Apr 2015 14:24:00 -0000	[thread overview]
Message-ID: <bug-65841-4-ehvjC2AgF1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65841-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I confirm the segfault with my clean trees for all variants (4.8 and 4.9 give
an ICE).

However I don't see them on my patched trees having Mikael's patch for pr65792
(https://gcc.gnu.org/ml/fortran/2015-04/msg00063.html) and Andre's one for
pr59678 (https://gcc.gnu.org/ml/fortran/2015-04/msg00061.html). Note that the
last test in comment 1 segfault with only the [fist patch] for pr65792 + the
one for pr59678.

All the test run without segfault with the cumulated patch for pr61831 and
pr65792 (https://gcc.gnu.org/bugzilla/attachment.cgi?id=35352) + the one for
pr59678.

Note also that repeated assignments is checked by
gfortran.dg/alloc_comp_assign_10.f90 (pr39879):

  u%model = u%design
  u%model = u%design ! The double assignment was the cause of the ICE


  parent reply	other threads:[~2015-04-22 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22  0:43 [Bug fortran/65841] New: " damian at sourceryinstitute dot org
2015-04-22 13:03 ` [Bug fortran/65841] " pault at gcc dot gnu.org
2015-04-22 14:24 ` dominiq at lps dot ens.fr [this message]
2015-04-23  7:39 ` dominiq at lps dot ens.fr
2015-04-27 17:34 ` vehre at gcc dot gnu.org
2015-05-05  9:10 ` vehre at gcc dot gnu.org
2015-10-18 15:01 ` mikael 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-65841-4-ehvjC2AgF1@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).