public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/15638] gcc should have option to treat missing headers as fatal Date: Tue, 31 Mar 2009 12:43:00 -0000 [thread overview] Message-ID: <20090331124347.32608.qmail@sourceware.org> (raw) In-Reply-To: <bug-15638-5711@http.gcc.gnu.org/bugzilla/> ------- Comment #15 from jsm28 at gcc dot gnu dot org 2009-03-31 12:43 ------- Subject: Bug 15638 Author: jsm28 Date: Tue Mar 31 12:43:29 2009 New Revision: 145341 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145341 Log: PR preprocessor/15638 gcc: * c-common.c (c_cpp_error): Handle CPP_DL_FATAL. gcc/fortran: * cpp.c (cb_cpp_error): Handle CPP_DL_FATAL. gcc/testsuite: * gcc.dg/cpp/missing-header-1.c: New test. * gcc.dg/cpp/include2.c: Only test #include <>. Expect "compilation terminated" message. * gcc.dg/cpp/include2a.c: New test. Copy of include2.c but only test #include "". * gcc.dg/pch/counter-2.c, gcc.dg/pch/valid-1.c, gcc.dg/pch/valid-2.c, gcc.dg/pch/warn-1.c: Expect "compilation terminated" message. libcpp: * files.c (_cpp_find_file): Call open_file_failed after diagnosing invalid PCH. (open_file_failed): Make error for missing file fatal. * include/cpplib.h (CPP_DL_FATAL): Define. Added: trunk/gcc/testsuite/gcc.dg/cpp/include2a.c trunk/gcc/testsuite/gcc.dg/cpp/missing-header-1.c Modified: trunk/gcc/ChangeLog trunk/gcc/c-common.c trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/cpp.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/cpp/include2.c trunk/gcc/testsuite/gcc.dg/pch/counter-2.c trunk/gcc/testsuite/gcc.dg/pch/valid-1.c trunk/gcc/testsuite/gcc.dg/pch/valid-2.c trunk/gcc/testsuite/gcc.dg/pch/warn-1.c trunk/libcpp/ChangeLog trunk/libcpp/files.c trunk/libcpp/include/cpplib.h -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15638
next prev parent reply other threads:[~2009-03-31 12:43 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-15638-5711@http.gcc.gnu.org/bugzilla/> 2007-02-15 17:51 ` pinskia at gcc dot gnu dot org 2007-03-28 16:37 ` bangerth at dealii dot org 2009-02-10 15:17 ` jsm28 at gcc dot gnu dot org 2009-02-10 15:24 ` manu at gcc dot gnu dot org 2009-02-10 15:35 ` joseph at codesourcery dot com 2009-02-11 1:16 ` joseph at codesourcery dot com 2009-03-31 12:43 ` jsm28 at gcc dot gnu dot org [this message] 2009-03-31 12:45 ` jsm28 at gcc dot gnu dot org [not found] <bug-15638-4@http.gcc.gnu.org/bugzilla/> 2014-04-03 7:44 ` eving.tw at gmail dot com 2014-04-03 8:11 ` pinskia at gcc dot gnu.org 2014-04-03 12:30 ` manu at gcc dot gnu.org 2014-04-03 18:02 ` eving.tw at gmail dot com 2014-04-03 19:39 ` redi at gcc dot gnu.org 2004-05-25 18:20 [Bug preprocessor/15638] New: " jlawson-gcc at bovine dot net 2004-05-25 18:25 ` [Bug preprocessor/15638] " pinskia at gcc dot gnu dot org 2004-05-28 22:04 ` neil at gcc dot gnu dot org 2004-05-28 22:05 ` falk at debian dot org 2004-05-28 22:36 ` pinskia at gcc dot gnu dot org 2004-05-29 0:13 ` bbrownstone at hotmail dot com 2004-05-29 1:31 ` bbrownstone at hotmail dot com 2004-05-29 2:55 ` zack at codesourcery dot com 2004-05-30 4:44 ` jlawson-gcc at bovine dot net 2004-06-26 20:21 ` pinskia 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=20090331124347.32608.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).