public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34656] modifies do loop variable
Date: Thu, 03 Jan 2008 22:04:00 -0000	[thread overview]
Message-ID: <20080103215149.5771.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34656-6642@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from steven at gcc dot gnu dot org  2008-01-03 21:51 -------
This is almost impossible to diagnose.  Do you know of any compiler that
detects this?

The only way I see to diagnose this, is to mark all do loop variables as such,
and warn about all assignments to such variables in contained functions.  But
that would result in false positives for e.g.

PROGRAM test
IMPLICIT NONE
INTEGER :: i
DO i=1,100
   CALL do_nothing()
ENDDO
CALL do_something()
CONTAINS
 SUBROUTINE do_something()
 IMPLICIT NONE
 DO i=1,10
 ENDDO
 END SUBROUTINE do_something
 SUBROUTINE do_nothing()
 IMPLICIT NONE
 END SUBROUTINE do_nothing
END PROGRAM test

which also seems undesirable... Thoughts?


-- 

steven at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2008-01-03 21:51:49
               date|                            |


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


  reply	other threads:[~2008-01-03 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03 20:17 [Bug fortran/34656] New: " jv244 at cam dot ac dot uk
2008-01-03 22:04 ` steven at gcc dot gnu dot org [this message]
2008-01-04  7:17 ` [Bug fortran/34656] " jv244 at cam dot ac dot uk
2008-01-04  7:23 ` burnus at gcc dot gnu dot org
2008-01-04  9:36 ` tkoenig at gcc dot gnu dot org
2009-03-28 21:39 ` burnus at gcc dot gnu dot org
2009-03-28 21:40 ` burnus 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=20080103215149.5771.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).