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/40011] Problems with -fwhole-file Date: Sat, 01 Aug 2009 13:45:00 -0000 [thread overview] Message-ID: <20090801134535.3178.qmail@sourceware.org> (raw) In-Reply-To: <bug-40011-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #43 from pault at gcc dot gnu dot org 2009-08-01 13:45 ------- Subject: Bug 40011 Author: pault Date: Sat Aug 1 13:45:12 2009 New Revision: 150333 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=150333 Log: 2009-08-01 Paul Thomas <pault@gcc.gnu.org> PR fortran/40011 * error.c : Add static flag 'warnings_not_errors'. (gfc_error): If 'warnings_not_errors' is set, branch to code from gfc_warning. (gfc_clear_error): Reset 'warnings_not_errors'. (gfc_errors_to_warnings): New function. * options.c (gfc_post_options): If pedantic and flag_whole_file change the latter to a value of 2. * parse.c (parse_module): Add module namespace to gsymbol. (resolve_all_program_units): New function. (clean_up_modules): New function. (translate_all_program_units): New function. (gfc_parse_file): If whole_file, do not clean up module right away and add derived types to namespace derived types. In addition, call the three new functions above. * resolve.c (not_in_recursive): New function. (not_entry_self_reference): New function. (resolve_global_procedure): Symbol must not be IFSRC_UNKNOWN, procedure must not be in the course of being resolved and must return false for the two new functions. Pack away the current derived type list before calling gfc_resolve for the gsymbol namespace. It is unconditionally an error if the ranks of the reference and ther procedure do not match. Convert errors to warnings during call to gfc_procedure_use if not pedantic or legacy. (gfc_resolve): Set namespace resolved flag to -1 during resolution and store current cs_base. * trans-decl.c (gfc_get_symbol_decl): If whole_file compilation substitute a use associated variable, if it is available in a gsymbolnamespace. (gfc_get_extern_function_decl): If the procedure is use assoc, do not attempt to find it in a gsymbol because it could be an interface. If the symbol exists in a module namespace, return its backend_decl. * trans-expr.c (gfc_trans_scalar_assign): If a derived type assignment, set the rhs TYPE_MAIN_VARIANT to that of the rhs. * trans-types.c (copy_dt_decls_ifequal): Add 'from_gsym' as a boolean argument. Copy component backend_decls directly if the components are derived types and from_gsym is true. (gfc_get_derived_type): If whole_file copy the derived type from the module if it is use associated, otherwise, if can be found in another gsymbol namespace, use the existing derived type as the TYPE_CANONICAL and build normally. * gfortran.h : Add derived_types and resolved fields to gfc_namespace. Include prototype for gfc_errors_to_warnings. 2009-08-01 Paul Thomas <pault@gcc.gnu.org> PR fortran/40011 * gfortran.dg/whole_file_7.f90: New test. * gfortran.dg/whole_file_8.f90: New test. * gfortran.dg/whole_file_9.f90: New test. * gfortran.dg/whole_file_10.f90: New test. * gfortran.dg/whole_file_11.f90: New test. * gfortran.dg/whole_file_12.f90: New test. * gfortran.dg/whole_file_13.f90: New test. * gfortran.dg/whole_file_14.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/whole_file_10.f90 trunk/gcc/testsuite/gfortran.dg/whole_file_11.f90 trunk/gcc/testsuite/gfortran.dg/whole_file_12.f90 trunk/gcc/testsuite/gfortran.dg/whole_file_13.f90 trunk/gcc/testsuite/gfortran.dg/whole_file_14.f90 trunk/gcc/testsuite/gfortran.dg/whole_file_7.f90 trunk/gcc/testsuite/gfortran.dg/whole_file_8.f90 trunk/gcc/testsuite/gfortran.dg/whole_file_9.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/error.c trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/options.c trunk/gcc/fortran/parse.c trunk/gcc/fortran/resolve.c trunk/gcc/fortran/trans-decl.c trunk/gcc/fortran/trans-expr.c trunk/gcc/fortran/trans-types.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40011
next prev parent reply other threads:[~2009-08-01 13:45 UTC|newest] Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-03 19:53 [Bug fortran/40011] New: " dominiq at lps dot ens dot fr 2009-05-04 9:10 ` [Bug fortran/40011] " pault at gcc dot gnu dot org 2009-05-04 9:29 ` pault at gcc dot gnu dot org 2009-05-04 9:31 ` pault at gcc dot gnu dot org 2009-05-04 17:55 ` dominiq at lps dot ens dot fr 2009-05-04 21:52 ` dominiq at lps dot ens dot fr 2009-05-04 22:20 ` dominiq at lps dot ens dot fr 2009-05-04 22:44 ` dominiq at lps dot ens dot fr 2009-05-05 4:18 ` jv244 at cam dot ac dot uk 2009-05-05 7:05 ` dominiq at lps dot ens dot fr 2009-05-05 7:06 ` dominiq at lps dot ens dot fr 2009-05-05 11:33 ` dominiq at lps dot ens dot fr 2009-05-05 15:57 ` dominiq at lps dot ens dot fr 2009-05-05 18:12 ` pault at gcc dot gnu dot org 2009-05-05 19:29 ` jv244 at cam dot ac dot uk 2009-05-07 18:00 ` dfranke at gcc dot gnu dot org 2009-05-07 18:34 ` dfranke at gcc dot gnu dot org 2009-05-08 14:09 ` dominiq at lps dot ens dot fr 2009-05-17 5:12 ` jv244 at cam dot ac dot uk 2009-05-22 13:40 ` pault at gcc dot gnu dot org 2009-05-25 6:13 ` jv244 at cam dot ac dot uk 2009-05-27 13:03 ` burnus at gcc dot gnu dot org 2009-05-27 14:05 ` dominiq at lps dot ens dot fr 2009-05-27 17:52 ` jv244 at cam dot ac dot uk 2009-05-29 15:34 ` pault at gcc dot gnu dot org 2009-05-29 16:34 ` jv244 at cam dot ac dot uk 2009-05-29 18:42 ` burnus at gcc dot gnu dot org 2009-05-30 8:27 ` pault at gcc dot gnu dot org 2009-06-01 18:01 ` pault at gcc dot gnu dot org 2009-06-01 19:34 ` jv244 at cam dot ac dot uk 2009-06-01 19:43 ` jv244 at cam dot ac dot uk 2009-06-02 9:29 ` dominiq at lps dot ens dot fr 2009-06-02 12:32 ` dominiq at lps dot ens dot fr 2009-06-14 16:58 ` rguenth at gcc dot gnu dot org 2009-07-24 5:39 ` jv244 at cam dot ac dot uk 2009-07-24 5:48 ` jv244 at cam dot ac dot uk 2009-07-24 10:25 ` rguenth at gcc dot gnu dot org 2009-07-24 10:28 ` rguenth at gcc dot gnu dot org 2009-07-24 10:57 ` rguenth at gcc dot gnu dot org 2009-07-24 11:29 ` jv244 at cam dot ac dot uk 2009-07-25 16:53 ` jv244 at cam dot ac dot uk 2009-07-26 21:23 ` rguenth at gcc dot gnu dot org 2009-07-28 7:37 ` jv244 at cam dot ac dot uk 2009-08-01 13:45 ` pault at gcc dot gnu dot org [this message] 2009-08-03 10:12 ` jv244 at cam dot ac dot uk 2009-08-26 9:24 ` jv244 at cam dot ac dot uk 2009-08-26 9:35 ` rguenther at suse dot de 2009-08-26 10:32 ` dominiq at lps dot ens dot fr 2009-08-26 10:34 ` dominiq at lps dot ens dot fr 2009-08-26 10:36 ` dominiq at lps dot ens dot fr 2009-10-11 12:46 ` jv244 at cam dot ac dot uk 2009-12-09 11:51 ` jv244 at cam dot ac dot uk 2009-12-09 11:52 ` rguenther at suse dot de 2010-05-03 10:57 ` jv244 at cam dot ac dot uk 2010-05-03 19:24 ` jvdelisle at gcc dot gnu dot org 2010-05-26 5:11 ` pault at gcc dot gnu dot org 2010-05-26 13:13 ` jv244 at cam dot ac dot uk 2010-05-26 14:53 ` dominiq at lps dot ens dot fr 2010-07-18 20:50 ` dfranke at gcc dot gnu dot org 2010-07-23 22:16 ` jv244 at cam dot ac dot uk 2010-07-23 22:55 ` jv244 at cam dot ac dot uk 2010-07-24 8:24 ` jv244 at cam dot ac dot uk 2010-07-24 11:11 ` jv244 at cam dot ac dot uk 2010-07-24 11:14 ` jv244 at cam dot ac dot uk 2010-07-24 11:31 ` burnus at gcc dot gnu dot org 2010-07-24 13:08 ` burnus at gcc dot gnu dot org 2010-07-24 13:46 ` rguenther at suse dot de 2010-07-24 14:08 ` burnus at gcc dot gnu dot org 2010-07-24 16:32 ` burnus at gcc dot gnu dot org 2010-07-25 1:21 ` jvdelisle at gcc dot gnu dot org 2010-07-25 10:11 ` burnus at gcc dot gnu dot org 2010-07-26 9:53 ` burnus at gcc dot gnu dot org 2010-07-26 13:15 ` burnus at gcc dot gnu dot org [not found] <bug-40011-4@http.gcc.gnu.org/bugzilla/> 2020-06-14 15:24 ` 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=20090801134535.3178.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).