public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vehre at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/59678] [F03] Segfault on equalizing variables of a complex derived type Date: Mon, 27 Apr 2015 17:34:00 -0000 [thread overview] Message-ID: <bug-59678-4-xjTi21lBCg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59678-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59678 --- Comment #17 from vehre at gcc dot gnu.org --- Author: vehre Date: Mon Apr 27 17:34:11 2015 New Revision: 222477 URL: https://gcc.gnu.org/viewcvs?rev=222477&root=gcc&view=rev Log: gcc/fortran 2015-04-27 Andre Vehreschild <vehre@gmx.de> PR fortran/59678 PR fortran/65841 * trans-array.c (duplicate_allocatable): Fixed deep copy of allocatable components, which are liable for copy only, when they are allocated. (gfc_duplicate_allocatable): Add deep-copy code into if component allocated block. Needed interface change for that. (gfc_copy_allocatable_data): Supplying NULL_TREE for code to add into if-block for checking whether a component was allocated. (gfc_duplicate_allocatable_nocopy): Likewise. (structure_alloc_comps): Likewise. * trans-array.h: Likewise. * trans-expr.c (gfc_trans_alloc_subarray_assign): Likewise. * trans-openmp.c (gfc_walk_alloc_comps): Likewise. gcc/testsuite 2015-04-27 Andre Vehreschild <vehre@gmx.de> PR fortran/59678 PR fortran/65841 * gfortran.dg/alloc_comp_deep_copy_1.f03: New test. * gfortran.dg/alloc_comp_deep_copy_2.f03: New test. Added: trunk/gcc/testsuite/gfortran.dg/alloc_comp_deep_copy_1.f03 trunk/gcc/testsuite/gfortran.dg/alloc_comp_deep_copy_2.f03 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-array.c trunk/gcc/fortran/trans-array.h trunk/gcc/fortran/trans-expr.c trunk/gcc/fortran/trans-openmp.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-04-27 17:34 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-04 23:38 [Bug fortran/59678] New: Segmentation fault on equalizing variables of a complex derived data type talebi.hossein at gmail dot com 2014-01-05 12:53 ` [Bug fortran/59678] " talebi.hossein at gmail dot com 2014-01-05 13:17 ` janus at gcc dot gnu.org 2014-01-05 14:30 ` talebi.hossein at gmail dot com 2014-01-05 15:45 ` dominiq at lps dot ens.fr 2014-01-05 17:32 ` talebi.hossein at gmail dot com 2014-01-05 20:18 ` dominiq at lps dot ens.fr 2014-01-05 20:25 ` talebi.hossein at gmail dot com 2014-01-12 20:14 ` talebi.hossein at gmail dot com 2014-01-12 20:19 ` talebi.hossein at gmail dot com 2014-01-12 20:43 ` [Bug fortran/59678] [F03] Segfault on equalizing variables of a complex derived type janus at gcc dot gnu.org 2014-01-12 20:44 ` dominiq at lps dot ens.fr 2014-01-12 20:46 ` dominiq at lps dot ens.fr 2014-01-12 20:54 ` janus at gcc dot gnu.org 2014-04-20 19:52 ` talebi.hossein at gmail dot com 2015-04-18 11:31 ` vehre at gcc dot gnu.org 2015-04-27 17:34 ` vehre at gcc dot gnu.org [this message] 2015-05-05 9:03 ` vehre at gcc dot gnu.org 2015-05-05 23:06 ` talebi.hossein at gmail dot com 2015-05-06 8:09 ` 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-59678-4-xjTi21lBCg@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).