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/55603] [F03] Memory leak with scalar allocatable function result Date: Fri, 25 Sep 2015 20:29:00 -0000 [thread overview] Message-ID: <bug-55603-4-XiYFfsB86N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55603-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55603 --- Comment #10 from Mikael Morin <mikael at gcc dot gnu.org> --- Author: mikael Date: Fri Sep 25 20:28:33 2015 New Revision: 228151 URL: https://gcc.gnu.org/viewcvs?rev=228151&root=gcc&view=rev Log: Add PR fortran/55603 working test gcc/testsuite/ PR fortran/55603 * gfortran.dg/allocatable_function_9.f90: New. Added: trunk/gcc/testsuite/gfortran.dg/allocatable_function_9.f90 Modified: trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-09-25 20:29 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-05 4:02 [Bug fortran/55603] New: Memory leak in intrinsic assignment of allocatable derived type " damian at rouson dot net 2012-12-05 8:26 ` [Bug fortran/55603] " janus at gcc dot gnu.org 2012-12-05 10:00 ` [Bug fortran/55603] Memory leak in intrinsic assignment of a scalar allocatable " burnus at gcc dot gnu.org 2012-12-05 10:14 ` burnus at gcc dot gnu.org 2012-12-28 16:02 ` janus at gcc dot gnu.org 2013-01-20 19:00 ` damian at rouson dot net 2013-08-25 14:46 ` burnus at gcc dot gnu.org 2013-08-25 14:47 ` burnus at gcc dot gnu.org 2015-01-03 12:56 ` [Bug fortran/55603] [F03] Memory leak with " janus at gcc dot gnu.org 2015-09-25 20:29 ` mikael at gcc dot gnu.org [this message] 2015-09-25 20:35 ` 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-55603-4-XiYFfsB86N@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).