public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pilot.mm at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/66932] New: Preprocessor includes wrong header file
Date: Sat, 18 Jul 2015 19:54:00 -0000	[thread overview]
Message-ID: <bug-66932-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66932

            Bug ID: 66932
           Summary: Preprocessor includes wrong header file
           Product: gcc
           Version: 4.9.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pilot.mm at gmail dot com
  Target Milestone: ---

Created attachment 36011
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36011&action=edit
The stripped down test case for the problem...

Hello Folks

      There seems to be an error in the preprocessor where the wrong header
file is included. This problem occurs several times when compiling binutils and
gcc with newer versions of gcc. I have successfully compiled both of these
projects with older versions. Furthermore I have confirmed with the binutils
people that this is in fact a gcc bug. For your convenience I have prepared a
stripped down version of the problem. The README explains this test case.

      Basically the problem occurs when there exists multiple header files with
the same name in different sub-folders (in my case it was 'config.h'). The
problem occurs when you compile one of the problems in the sub folder. This
occurs when a -I directive to one of the other sub-folders is given.
Furthermore this occurs when the duplicate header file is included indirectly.
It seems binutils and gcc assumes that the version in the local directory
should be included. Instead the preprocessor includes the one in the other
sub-folder.

      I hope my explanation makes sense. I have created a stripped down version
for you folks to understand the problem and hopefully fix it.

Take Care
Mike


             reply	other threads:[~2015-07-18 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-18 19:54 pilot.mm at gmail dot com [this message]
2015-07-19  2:49 ` [Bug preprocessor/66932] " pinskia at gcc dot gnu.org
2015-07-19 13:42 ` redi at gcc dot gnu.org
2015-07-19 17:51 ` pilot.mm at gmail dot com
2015-07-20  9:27 ` pinskia at gcc dot gnu.org
2021-07-18 23:03 ` pinskia 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-66932-4@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).