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/44354] implied do loop with its own variable name as upper bound
Date: Thu, 26 Jul 2012 08:48:00 -0000	[thread overview]
Message-ID: <bug-44354-4-9eTxtSzmw6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44354-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #23 from Mikael Morin <mikael at gcc dot gnu.org> 2012-07-26 08:47:42 UTC ---
Author: mikael
Date: Thu Jul 26 08:47:33 2012
New Revision: 189882

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=189882
Log:
fortran/
    PR fortran/44354
    * array.c (sought_symbol): New variable.
    (expr_is_sought_symbol_ref, find_symbol_in_expr): New functions.
    (resolve_array_list): Check for references to the induction
    variable in the iteration bounds and issue a diagnostic if some
    are found.

testsuite/
    PR fortran/44354
    * gfortran.dg/array_constructor_38.f90: New test.



Added:
    trunk/gcc/testsuite/gfortran.dg/array_constructor_38.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/array.c
    trunk/gcc/testsuite/ChangeLog


       reply	other threads:[~2012-07-26  8:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44354-4@http.gcc.gnu.org/bugzilla/>
2012-07-26  8:48 ` mikael at gcc dot gnu.org [this message]
2012-07-26  8:54 ` mikael at gcc dot gnu.org
2012-07-26  9:05 ` mikael at gcc dot gnu.org
2010-05-31 16:32 [Bug fortran/44354] New: incorrect output at run time zeccav at gmail dot com
2010-06-07 18:11 ` [Bug fortran/44354] implied do loop with its own variable name as upper bound tkoenig at gcc dot gnu dot org
2010-07-28 20:54 ` mikael 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=bug-44354-4-9eTxtSzmw6@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: 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).