public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51502] [4.6/4.7 Regression] Potentially wrong code generation due to wrong implict_pure check
Date: Sat, 31 Dec 2011 08:50:00 -0000 [thread overview]
Message-ID: <bug-51502-4-I3jT9sF7ls@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51502-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51502
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2011-12-31 08:19:01 UTC ---
Author: tkoenig
Date: Sat Dec 31 08:18:52 2011
New Revision: 182754
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=182754
Log:
2011-12-31 Thomas König <tkoenig@gcc.gnu.org>
PR fortran/51502
* expr.c (gfc_check_vardef_context): When determining
implicit pure status, also check for variable definition
context. Walk up namespaces until a procedure is
found to reset the implict pure attribute.
* resolve.c (gfc_implicit_pure): Walk up namespaces
until a procedure is found.
2011-12-31 Thomas König <tkoenig@gcc.gnu.org>
PR fortran/51502
* lib/gcc-dg.exp (scan-module-absence): New function.
* gfortran.dg/implicit_pure_2.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/implicit_pure_2.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/expr.c
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2011-12-31 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 17:15 [Bug fortran/51502] New: [4.6/4.7 Regression] Potentially wrong code " burnus at gcc dot gnu.org
2011-12-11 17:43 ` [Bug fortran/51502] [4.6/4.7 Regression] Potentially wrong code generation " burnus at gcc dot gnu.org
2011-12-11 20:36 ` tkoenig at gcc dot gnu.org
2011-12-11 21:01 ` tkoenig at gcc dot gnu.org
2011-12-12 8:20 ` jakub at gcc dot gnu.org
2011-12-28 22:52 ` tkoenig at gcc dot gnu.org
2011-12-31 8:50 ` tkoenig at gcc dot gnu.org [this message]
2012-01-01 16:13 ` tkoenig at gcc dot gnu.org
2012-01-01 16:14 ` tkoenig at gcc dot gnu.org
2012-01-01 16:28 ` tkoenig at gcc dot gnu.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-51502-4-I3jT9sF7ls@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).