public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/27470] [4.1/4.2 regression] wrong memory allocator for derived types
Date: Wed, 10 May 2006 18:27:00 -0000 [thread overview]
Message-ID: <20060510182700.2978.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27470-10391@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from tkoenig at gcc dot gnu dot org 2006-05-10 18:27 -------
Subject: Bug 27470
Author: tkoenig
Date: Wed May 10 18:26:51 2006
New Revision: 113680
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113680
Log:
2005-05-10 Thomas Koenig <Thomas.Koenig@online.de>
PR fortran/27470
* trans-array.c(gfc_array_allocate): If ref->next exists
that is if there is a statement like ALLOCATE(foo%bar(2)),
F95 rules require that bar should be a pointer.
2005-05-10 Thomas Koenig <Thomas.Koenig@online.de>
PR fortran/27470
* gfortran.dg/multiple_allocation_2.f90: New test case.
Added:
trunk/gcc/testsuite/gfortran.dg/multiple_allocation_2.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27470
next prev parent reply other threads:[~2006-05-10 18:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 9:41 [Bug fortran/27470] New: [4.1 4.2 regression] wong " tkoenig at gcc dot gnu dot org
2006-05-07 17:31 ` [Bug fortran/27470] [4.1/4.2 " pinskia at gcc dot gnu dot org
2006-05-07 19:36 ` tkoenig at gcc dot gnu dot org
2006-05-08 21:06 ` [Bug fortran/27470] [4.1/4.2 regression] wrong " tkoenig at gcc dot gnu dot org
2006-05-08 22:00 ` tkoenig at gcc dot gnu dot org
2006-05-08 22:11 ` tkoenig at gcc dot gnu dot org
2006-05-10 18:27 ` tkoenig at gcc dot gnu dot org [this message]
2006-05-14 22:35 ` mmitchel at gcc dot gnu dot org
2006-05-15 19:39 ` patchapp at dberlin dot org
2006-05-25 2:47 ` [Bug fortran/27470] [4.1 " mmitchel at gcc dot gnu dot org
2006-05-27 21:25 ` tkoenig at gcc dot gnu dot org
2006-05-28 12:33 ` tkoenig at gcc dot gnu dot org
2006-05-28 20:36 ` tkoenig at gcc dot gnu dot org
2006-05-28 20:37 ` tkoenig at gcc dot gnu dot org
2006-06-28 18:50 ` jjcogliati-r1 at yahoo dot com
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=20060510182700.2978.qmail@sourceware.org \
--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: link
Be 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).