public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mbland at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/26857] New: Warning for absolute or dotted header paths Date: Fri, 24 Mar 2006 23:33:00 -0000 [thread overview] Message-ID: <bug-26857-12407@http.gcc.gnu.org/bugzilla/> (raw) Given that some build systems try to encapsulate system headers separately from those found in /usr/include, primarily through careful arrangement of -I flags, it would be helpful if there was a warning flag, let's call it -Wstrict-header-path for now, which would signal when a source file tries to do the following: #include "/usr/include/sys/stat.h" #include "../../../sys/stat.h" Ian Lance Taylor has indicated to me that this could be done as a check on fname in do_include_common in libcpp/directives.c. I would be willing to attempt a patch myself if this enhancement is accepted. -- Summary: Warning for absolute or dotted header paths Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: preprocessor AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mbland at google dot com GCC build triplet: N/A GCC host triplet: N/A GCC target triplet: N/A http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26857
next reply other threads:[~2006-03-24 23:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-24 23:33 mbland at google dot com [this message] 2006-03-27 19:25 ` [Bug preprocessor/26857] " mbland at google dot com 2006-03-30 20:12 ` pinskia at gcc dot gnu dot org 2006-03-30 21:09 ` mbland at google dot com 2007-01-08 19:53 ` tromey at gcc dot gnu dot org 2007-01-08 19:58 ` mbland at google dot com
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-26857-12407@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).