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/25031] [4.1 only] Allocatable array can be reallocated. Date: Sat, 08 Apr 2006 17:05:00 -0000 [thread overview] Message-ID: <20060408170557.9264.qmail@sourceware.org> (raw) In-Reply-To: <bug-25031-9795@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from tkoenig at gcc dot gnu dot org 2006-04-08 17:05 ------- Subject: Bug 25031 Author: tkoenig Date: Sat Apr 8 17:05:52 2006 New Revision: 112783 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112783 Log: 2006-04-08 Thomas Koenig <Thomas.Koenig@online.de> PR fortran/25031 Backport from mainline * trans-array.h: Adjust gfc_array_allocate prototype. * trans-array.c (gfc_array_allocate): Change type of gfc_array_allocatate to bool. Function returns true if it operates on an array. Change second argument to gfc_expr. Find last reference in chain. If the function operates on an allocatable array, emit call to allocate_array() or allocate64_array(). * trans-stmt.c (gfc_trans_allocate): Code to follow to last reference has been moved to gfc_array_allocate. * trans.h: Add declaration for gfor_fndecl_allocate_array and gfor_fndecl_allocate64_array. (gfc_build_builtin_function_decls): Add gfor_fndecl_allocate_array and gfor_fndecl_allocate64_array. 2006-04-08 Thomas Koenig <Thomas.Koenig@online.de> PR fortran/25031 Backport from mainline * runtime/memory.c: Adjust copyright years. (allocate_array): New function. (allocate64_array): New function. * libgfortran.h (error_codes): Add ERROR_ALLOCATION. 2006-04-08 Thomas Koenig <Thomas.Koenig@online.de> PR fortran/25031 * gfortran.dg/multiple_allocation_1.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/multiple_allocation_1.f90 Modified: branches/gcc-4_1-branch/gcc/fortran/ChangeLog branches/gcc-4_1-branch/gcc/fortran/trans-array.c branches/gcc-4_1-branch/gcc/fortran/trans-array.h branches/gcc-4_1-branch/gcc/fortran/trans-decl.c branches/gcc-4_1-branch/gcc/fortran/trans-stmt.c branches/gcc-4_1-branch/gcc/fortran/trans.h branches/gcc-4_1-branch/gcc/testsuite/ChangeLog branches/gcc-4_1-branch/libgfortran/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25031
next prev parent reply other threads:[~2006-04-08 17:05 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-25 9:00 [Bug fortran/25031] New: " iguchi at coral dot t dot u-tokyo dot ac dot jp 2005-11-25 15:09 ` [Bug fortran/25031] " eedelman at gcc dot gnu dot org 2006-01-28 18:49 ` tkoenig at gcc dot gnu dot org 2006-03-03 16:18 ` tkoenig at gcc dot gnu dot org 2006-03-23 18:36 ` tkoenig at gcc dot gnu dot org 2006-03-30 16:30 ` tkoenig at gcc dot gnu dot org 2006-04-08 17:05 ` tkoenig at gcc dot gnu dot org [this message] 2006-04-08 17:06 ` [Bug fortran/25031] [4.1 only] " tkoenig at gcc dot gnu dot org 2006-04-09 9:00 ` tkoenig at gcc dot gnu dot org 2006-04-12 1:23 ` pinskia at gcc dot gnu dot 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=20060408170557.9264.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: 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).