public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55534] -Wno-missing-include-dirs does not work with gfortran Date: Wed, 05 Dec 2012 09:29:00 -0000 [thread overview] Message-ID: <bug-55534-4-CMyribzt1x@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55534-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55534 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org, | |tkoenig at gcc dot gnu.org --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-12-05 09:29:08 UTC --- (See PR 54033 for the patch which originally added this feature.) Untested patch. --- a/gcc/fortran/cpp.c +++ b/gcc/fortran/cpp.c @@ -471,2 +471,3 @@ gfc_cpp_post_options (void) cpp_option->preprocessed = gfc_option.flag_preprocessed; + cpp_option->warn_missing_include_dirs = gfc_option.warn_missing_include_dirs; diff --git a/gcc/fortran/gfortran.h b/gcc/fortran/gfortran.h index bf767b2..6f3515f 100644 --- a/gcc/fortran/gfortran.h +++ b/gcc/fortran/gfortran.h @@ -2236,2 +2236,3 @@ typedef struct int warn_target_lifetime; + int warn_missing_include_dirs; int max_errors; diff --git a/gcc/fortran/options.c b/gcc/fortran/options.c index e05b935..489d1ff 100644 --- a/gcc/fortran/options.c +++ b/gcc/fortran/options.c @@ -117,2 +117,3 @@ gfc_init_options (unsigned int decoded_options_count, gfc_option.warn_target_lifetime = 0; + gfc_option.warn_missing_include_dirs = 0; gfc_option.max_errors = 25; @@ -478,2 +485,3 @@ set_Wall (int setting) gfc_option.warn_target_lifetime = setting; + gfc_option.warn_missing_include_dirs = setting; @@ -686,2 +694,6 @@ gfc_handle_option (size_t scode, const char *arg, int value, + case OPT_Wmissing_include_dirs: + gfc_option.warn_missing_include_dirs = value; + break; + case OPT_Wrealloc_lhs: diff --git a/gcc/fortran/scanner.c b/gcc/fortran/scanner.c index 765c0f9..2bdd87f 100644 --- a/gcc/fortran/scanner.c +++ b/gcc/fortran/scanner.c @@ -327,4 +327,3 @@ add_path_to_list (gfc_directorylist **list, const char *path, { - /* FIXME: Also support -Wmissing-include-dirs. */ - if (warn) + if (warn && gfc_option.warn_missing_include_dirs) gfc_warning_now ("Nonexistent include directory \"%s\"", path);
next prev parent reply other threads:[~2012-12-05 9:29 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-29 20:31 [Bug fortran/55534] New: " anlauf at gmx dot de 2012-11-29 20:32 ` [Bug fortran/55534] " anlauf at gmx dot de 2012-12-04 23:02 ` anlauf at gmx dot de 2012-12-05 9:29 ` burnus at gcc dot gnu.org [this message] 2012-12-05 21:44 ` anlauf at gmx dot de 2012-12-06 0:04 ` burnus at gcc dot gnu.org 2012-12-07 21:10 ` anlauf at gmx dot de 2012-12-13 21:11 ` anlauf at gmx dot de 2014-09-09 21:39 ` manu at gcc dot gnu.org 2014-12-29 20:00 ` anlauf at gmx dot de 2014-12-29 21:28 ` manu at gcc dot gnu.org 2021-09-17 9:42 ` burnus at gcc dot gnu.org 2021-09-17 13:02 ` burnus at gcc dot gnu.org 2021-09-21 6:28 ` cvs-commit at gcc dot gnu.org 2021-09-21 7:13 ` burnus at gcc dot gnu.org 2021-09-22 18:58 ` cvs-commit at gcc dot gnu.org 2021-09-24 7:31 ` cvs-commit 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-55534-4-CMyribzt1x@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: 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).