public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54033] gfortran: Passing file as include directory - add diagnostic and ICE with -cpp
Date: Sat, 04 Aug 2012 18:27:00 -0000	[thread overview]
Message-ID: <bug-54033-4-tcYbpJUzSL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54033-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54033

--- Comment #4 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> 2012-08-04 18:27:04 UTC ---
Author: hjl
Date: Sat Aug  4 18:26:56 2012
New Revision: 190144

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=190144
Log:
Fix PR 54033, problems with -I, with test cases

     PR fortran/54033
     * scanner.c (add_path_to_list):  New argument warn.  Don't
     warn if it is true.
     (gfc_add_include_path):  Warn if directory is missing.
     (gfc_add_intrinsic_modules_path):  Do not warn if directory
     is missing.
     * optinons.c (gfc_handle_option):  Do not add directory
     for intrinsic modules to normal include path.

Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/options.c
    trunk/gcc/fortran/scanner.c


  parent reply	other threads:[~2012-08-04 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 14:30 [Bug fortran/54033] New: " burnus at gcc dot gnu.org
2012-07-22 20:06 ` [Bug fortran/54033] " tkoenig at gcc dot gnu.org
2012-08-01 21:44 ` tkoenig at gcc dot gnu.org
2012-08-01 21:46 ` tkoenig at gcc dot gnu.org
2012-08-04 18:27 ` hjl at gcc dot gnu.org [this message]
2013-01-20 12:34 ` 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=bug-54033-4-tcYbpJUzSL@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).