public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/56136] [OOP] ICE on lhs-reallocation of an object with overloaded (elemental) assignment operator Date: Sat, 15 Jun 2013 21:25:00 -0000 [thread overview] Message-ID: <bug-56136-4-6yFSU5Vgo0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56136-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56136 --- Comment #4 from Mikael Morin <mikael at gcc dot gnu.org> --- Author: mikael Date: Sat Jun 15 21:20:29 2013 New Revision: 200128 URL: http://gcc.gnu.org/viewcvs?rev=200128&root=gcc&view=rev Log: fortran/ PR fortran/49074 PR fortran/56136 * dependency.c (gfc_check_argument_var_dependency): Return 0 in the array constructor case. testsuite/ PR fortran/49074 PR fortran/56136 * gfortran.dg/typebound_assignment_5.f03: Check the absence of any packing. * gfortran.dg/typebound_assignment_6.f03: New. Added: trunk/gcc/testsuite/gfortran.dg/typebound_assignment_6.f03 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/dependency.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/typebound_assignment_5.f03
next prev parent reply other threads:[~2013-06-15 21:25 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-29 3:12 [Bug fortran/56136] New: Compiler fails when code contains lhs-reallocation of an object with overloaded (elemental) Assignment operator alipasha.celeris at gmail dot com 2013-01-29 8:39 ` [Bug fortran/56136] [OOP] ICE on lhs-reallocation of an object with overloaded (elemental) assignment operator janus at gcc dot gnu.org 2013-06-14 15:17 ` dominiq at lps dot ens.fr 2013-06-15 10:59 ` mikael at gcc dot gnu.org 2013-06-15 21:25 ` mikael at gcc dot gnu.org [this message] 2013-06-15 21:28 ` 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-56136-4-6yFSU5Vgo0@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).