public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/20779] ALLOCATEing the STAT variable not detected
Date: Tue, 03 Oct 2006 21:40:00 -0000	[thread overview]
Message-ID: <20061003214033.15137.qmail@sourceware.org> (raw)
In-Reply-To: <bug-20779-8513@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from pault at gcc dot gnu dot org  2006-10-03 21:40 -------
Subject: Bug 20779

Author: pault
Date: Tue Oct  3 21:40:24 2006
New Revision: 117415

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=117415
Log:
2006-10-03  Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/20779
        PR fortran/20891
        * resolve.c (find_sym_in_expr): New function that returns true
        if a symbol is found in an expression.
        (resolve_allocate_expr): Check whether the STAT variable is
        itself allocated in the same statement.  Use the call above to
        check whether any of the allocated arrays are used in array
        specifications in the same statement.

2006-10-03  Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/20779
        PR fortran/20891
        * gfortran.dg/alloc_alloc_expr_1.f90: New test.

Added:
    trunk/gcc/testsuite/gfortran.dg/alloc_alloc_expr_1.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/resolve.c
    trunk/gcc/testsuite/ChangeLog


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20779


  parent reply	other threads:[~2006-10-03 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-20779-8513@http.gcc.gnu.org/bugzilla/>
2006-09-05 19:39 ` pault at gcc dot gnu dot org
2006-09-17 17:40 ` patchapp at dberlin dot org
2006-10-03 21:40 ` pault at gcc dot gnu dot org [this message]
2006-10-03 21:41 ` pault at gcc dot gnu dot org
2005-04-05 23:10 [Bug fortran/20779] New: " tobi at gcc dot gnu dot org
2005-04-05 23:11 ` [Bug fortran/20779] " tobi at gcc dot gnu dot org
2005-04-05 23:35 ` 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=20061003214033.15137.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).