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/65841] Seg fault on intrinsic assignment to allocatable derived type with allocatable component Date: Wed, 22 Apr 2015 13:03:00 -0000 [thread overview] Message-ID: <bug-65841-4-AHgRpzo6yr@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 Paul Thomas <pault at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-04-22 CC| |pault at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Paul Thomas <pault at gcc dot gnu.org> --- Confirmed type a real, allocatable :: f end type type b type(a), allocatable :: g end type type(b) c,d c%g=a(1.) d=c d%g%f = 2.0 ! This causes the segfault too end However, if I make c and d allocatable type a real, allocatable :: f end type type b type(a), allocatable :: g end type type(b), allocatable :: c, d ! Note allocatable now allocate (c) c%g = a (1.) d = c d = c end ... it does not segfault. Note both must be allocatable for this to work. This should be a clue but I still do not see what is wrong with the code produced for the segfaulting cases. More staring at it tonight! Thanks for the report Paul
next prev parent reply other threads:[~2015-04-22 13:03 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 ` pault at gcc dot gnu.org [this message] 2015-04-22 14:24 ` [Bug fortran/65841] " dominiq at lps dot ens.fr 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-AHgRpzo6yr@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).