public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "langton at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/20441] -finit-local-zero is missing from gfortran
Date: Fri, 21 Sep 2007 02:34:00 -0000 [thread overview]
Message-ID: <20070921023426.31743.qmail@sourceware.org> (raw)
In-Reply-To: <bug-20441-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from langton at gcc dot gnu dot org 2007-09-21 02:34 -------
Subject: Bug 20441
Author: langton
Date: Fri Sep 21 02:34:14 2007
New Revision: 128643
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128643
Log:
PR fortran/20441
* gfortran.h : Add init_local_* enums and init_flag_* flags to
gfc_option_t.
* lang.opt: Add -finit-local-zero, -finit-real, -finit-integer,
-finit-character, and -finit-logical flags.
* invoke.texi: Document new options.
* resolve.c (build_init_assign): New function.
(apply_init_assign): Move part of function into build_init_assign.
(build_default_init_expr): Build local initializer (-finit-*).
(apply_default_init_local): Apply local initializer (-finit-*).
(resolve_fl_variable): Try to add local initializer (-finit-*).
* options.c (gfc_init_options, gfc_handle_option,
gfc_post_options): Handle -finit-local-zero, -finit-real,
-finit-integer, -finit-character, and -finit-logical flags.
PR fortran/20441
* gfortran.dg/init_flag_1.f90: New.
* gfortran.dg/init_flag_2.f90: New.
* gfortran.dg/init_flag_3.f90: New.
* gfortran.dg/init_flag_4.f90: New.
* gfortran.dg/init_flag_5.f90: New.
* gfortran.dg/init_flag_6.f90: New.
* gfortran.dg/init_flag_7.f90: New.
Added:
trunk/gcc/testsuite/gfortran.dg/init_flag_1.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_2.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_3.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_4.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_5.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_6.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_7.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/gfortran.h
trunk/gcc/fortran/invoke.texi
trunk/gcc/fortran/lang.opt
trunk/gcc/fortran/options.c
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20441
next prev parent reply other threads:[~2007-09-21 2:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-20441-6528@http.gcc.gnu.org/bugzilla/>
2006-02-07 12:48 ` fxcoudert at gcc dot gnu dot org
2006-08-20 20:51 ` tobias dot burnus at physik dot fu-berlin dot de
2006-08-21 1:38 ` pinskia at gcc dot gnu dot org
2006-11-27 16:03 ` burnus at gcc dot gnu dot org
2006-11-27 16:47 ` pinskia at gcc dot gnu dot org
2006-11-30 22:57 ` tkoenig at gcc dot gnu dot org
2007-06-18 16:23 ` langton at gcc dot gnu dot org
2007-08-17 20:15 ` patchapp at dberlin dot org
2007-08-20 12:29 ` arnaud02 at users dot sourceforge dot net
2007-08-20 15:07 ` langton at gcc dot gnu dot org
2007-09-21 2:34 ` langton at gcc dot gnu dot org [this message]
2007-09-21 2:40 ` langton at gcc dot gnu dot org
2005-03-12 17:11 [Bug fortran/20441] New: " pinskia at gcc dot gnu dot org
2005-03-12 22:54 ` [Bug fortran/20441] " tobi at gcc dot gnu dot org
2005-03-14 18:05 ` dir at lanl dot gov
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=20070921023426.31743.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).