public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/26227] accepts invalid fortran, different dummy types/number Date: Mon, 30 Mar 2009 19:36:00 -0000 [thread overview] Message-ID: <20090330193542.22825.qmail@sourceware.org> (raw) In-Reply-To: <bug-26227-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from pault at gcc dot gnu dot org 2009-03-30 19:35 ------- Subject: Bug 26227 Author: pault Date: Mon Mar 30 19:35:14 2009 New Revision: 145314 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145314 Log: 2009-03-30 Paul Thomas <pault@gcc.gnu.org> PR fortran/22571 PR fortran/26227 PR fortran/24886 * symbol.c : Add gfc_global_ns_list. * decl.c (add_global_entry): Set the namespace ('ns') field. * gfortran.h : Add the resolved field to gfc_namespace. Add the namespace ('ns') field to gfc_gsymbol. Add flag_whole_file to gfc_option_t. Add the prototype for gfc_free_dt_list. * lang.opt : Add the whole-file option. * invoke.texi : Document the whole-file option. * resolve.c (resolve_global_procedure): If the fwhole-file option is set, reorder gsymbols to ensure that translation is in the right order. Resolve the gsymbol's namespace if that has not occurred and then check interfaces. (resolve_function): Move call to resolve_global_procedure. (resolve_call): The same. (resolve_codes): Store the current labels_obstack. (gfc_resolve) : Return if the namespace is already resolved. trans-decl.c (gfc_get_extern_function_decl): If the whole_file option is selected, use the backend_decl of a gsymbol, if it is available. parse.c (add_global_procedure, add_global_program): If the flag whole-file is set, add the namespace to the gsymbol. (gfc_parse_file): On -fwhole-file, put procedure namespaces on the global namespace list. Rearrange to do resolution of all the procedures in a file, followed by their translation. * options.c (gfc_init_options): Add -fwhole-file. (gfc_handle_option): The same. 2009-03-30 Paul Thomas <pault@gcc.gnu.org> PR fortran/22571 * gfortran.dg/whole_file_1.f90: New test. PR fortran/26227 * gfortran.dg/whole_file_2.f90: New test. * gfortran.dg/whole_file_3.f90: New test. PR fortran/24886 * gfortran.dg/whole_file_4.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/whole_file_1.f90 trunk/gcc/testsuite/gfortran.dg/whole_file_2.f90 trunk/gcc/testsuite/gfortran.dg/whole_file_3.f90 trunk/gcc/testsuite/gfortran.dg/whole_file_4.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/decl.c trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/invoke.texi trunk/gcc/fortran/lang.opt trunk/gcc/fortran/options.c trunk/gcc/fortran/parse.c trunk/gcc/fortran/resolve.c trunk/gcc/fortran/symbol.c trunk/gcc/fortran/trans-array.c trunk/gcc/fortran/trans-decl.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26227
next prev parent reply other threads:[~2009-03-30 19:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-11 21:23 [Bug fortran/26227] New: " pinskia at gcc dot gnu dot org 2006-04-04 1:37 ` [Bug fortran/26227] " pinskia at gcc dot gnu dot org 2006-04-04 4:42 ` paulthomas2 at wanadoo dot fr 2006-05-13 22:26 ` pinskia at gcc dot gnu dot org 2006-05-13 23:05 ` pinskia at gcc dot gnu dot org 2006-05-13 23:19 ` pinskia at gcc dot gnu dot org 2006-09-13 16:11 ` tobi at gcc dot gnu dot org 2006-09-13 16:12 ` tobi at gcc dot gnu dot org 2007-03-12 19:09 ` burnus at gcc dot gnu dot org 2007-04-05 12:27 ` burnus at gcc dot gnu dot org 2007-06-01 15:21 ` burnus at gcc dot gnu dot org 2009-03-30 19:36 ` pault at gcc dot gnu dot org [this message] 2009-03-30 22:01 ` dominiq at lps dot ens dot fr 2010-05-19 21:54 ` tkoenig at gcc dot gnu dot org 2010-05-24 14:03 ` dfranke 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=20090330193542.22825.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: linkBe 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).