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/65532] [5 Regression] Unexpected error with legacy code (D1MACH)
Date: Wed, 25 Mar 2015 11:08:00 -0000 [thread overview]
Message-ID: <bug-65532-4-w7zqxtDjrX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65532-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65532
--- Comment #7 from Mikael Morin <mikael at gcc dot gnu.org> ---
Author: mikael
Date: Wed Mar 25 10:15:46 2015
New Revision: 221657
URL: https://gcc.gnu.org/viewcvs?rev=221657&root=gcc&view=rev
Log:
Fix regression introduced at revision 221586.
PR fortran/64952
PR fortran/65532
fortran/
* gfortran.h (struct gfc_namespace): New field 'types_resolved'.
* resolve.c (resolve_types): Return early if field 'types_resolved'
is set. Set 'types_resolved' at the end.
testsuite/
* gfortran.dg/data_initialized_3.f90: New.
Added:
trunk/gcc/testsuite/gfortran.dg/data_initialized_3.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/gfortran.h
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-03-25 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 0:55 [Bug fortran/65532] New: " anlauf at gmx dot de
2015-03-24 2:08 ` [Bug fortran/65532] " anlauf at gmx dot de
2015-03-24 2:09 ` dominiq at lps dot ens.fr
2015-03-24 7:44 ` jakub at gcc dot gnu.org
2015-03-24 11:40 ` mikael at gcc dot gnu.org
2015-03-24 13:39 ` mikael at gcc dot gnu.org
2015-03-24 14:09 ` ktkachov at gcc dot gnu.org
2015-03-25 2:54 ` mikael at gcc dot gnu.org
2015-03-25 11:08 ` mikael at gcc dot gnu.org [this message]
2015-03-26 13:01 ` mikael 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-65532-4-w7zqxtDjrX@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).