public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57360] Implement a warning for implied save
Date: Wed, 21 Oct 2015 19:11:00 -0000	[thread overview]
Message-ID: <bug-57360-4-5crVFEz9xu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57360-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360

Harald Anlauf <anlauf at gmx dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anlauf at gmx dot de

--- Comment #2 from Harald Anlauf <anlauf at gmx dot de> ---
I have a quite common "counter example", where a subroutine
is initialized on first invocation:

subroutine foo ()
  logical :: first = .true.
  write(6,*) first
  if (first) then
    first = .false.
    ! Do initialization
  end if
end subroutine foo

call foo ()
call foo ()
end

Should this one also get a warning?


  parent reply	other threads:[~2015-10-21 19:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 18:42 [Bug fortran/57360] New: " Joost.VandeVondele at mat dot ethz.ch
2015-10-20 21:46 ` [Bug fortran/57360] " dominiq at lps dot ens.fr
2015-10-21 19:11 ` anlauf at gmx dot de [this message]
2015-10-22  5:45 ` Joost.VandeVondele at mat dot ethz.ch
2021-10-07 20:41 ` anlauf at gcc dot gnu.org
2024-01-20 18:51 ` w6ws at earthlink dot net
2024-01-20 22:16 ` kargl at gcc dot gnu.org
2024-01-21 17:43 ` kargl at gcc dot gnu.org
2024-01-21 17:57 ` w6ws at earthlink dot net
2024-01-23 17:17 ` w6ws at earthlink dot net

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-57360-4-5crVFEz9xu@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).