public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51972] [OOP] Wrong code as _copy does not honor CLASS components Date: Sun, 29 Jan 2012 21:25:00 -0000 [thread overview] Message-ID: <bug-51972-4-VvevMvLZcP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51972-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51972 --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-29 20:02:25 UTC --- Author: burnus Date: Sun Jan 29 20:02:19 2012 New Revision: 183680 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183680 Log: 2012-01-29 Tobias Burnus <burnus@net-b.de> PR fortran/51972 * trans-array.c (structure_alloc_comps): Fix assignment of polymorphic components (polymorphic deep copying). 2012-01-29 Tobias Burnus <burnus@net-b.de> PR fortran/51972 * gfortran.dg/class_allocate_12.f90: Enable disabled test. * gfortran.dg/class_48.f90: New. Added: trunk/gcc/testsuite/gfortran.dg/class_48.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-array.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/class_allocate_12.f90
next prev parent reply other threads:[~2012-01-29 20:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-23 17:44 [Bug fortran/51972] New: [OOP] ALLOCATE misses memset/calloc, causing segfault burnus at gcc dot gnu.org 2012-01-28 16:50 ` [Bug fortran/51972] " burnus at gcc dot gnu.org 2012-01-28 17:42 ` burnus at gcc dot gnu.org 2012-01-28 19:01 ` burnus at gcc dot gnu.org 2012-01-29 21:25 ` burnus at gcc dot gnu.org [this message] 2012-01-29 21:42 ` [Bug fortran/51972] [OOP] Wrong code as _copy does not honor CLASS components burnus at gcc dot gnu.org 2012-02-05 9:46 ` burnus 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-51972-4-VvevMvLZcP@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).