public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rswan at signetic dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/33473]  New: GCC does not correctly generate dependencies correctly for precompiled headers
Date: Tue, 18 Sep 2007 13:33:00 -0000	[thread overview]
Message-ID: <bug-33473-15111@http.gcc.gnu.org/bugzilla/> (raw)

Hello;

GCC does not correctly generate dependencies correctly with g++ -MD when
precompiled headers are used. I've attached an example which generates main.d
while compiling main.cpp. main.cpp includes include/bink.h. When the include
path contains the precompiled bink.h.gch (only), main.d does not contain any
dependency on bink.h.gch.

When the compiler includes bink.h, main.d includes the dependency.

I get the same behavior with version 3.4.6 and 4.1.2

> gcc --version
gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)


-- 
           Summary: GCC does not correctly generate dependencies correctly
                    for precompiled headers
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rswan at signetic dot ca


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


             reply	other threads:[~2007-09-18 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18 13:33 rswan at signetic dot ca [this message]
2007-09-18 13:38 ` [Bug preprocessor/33473] " rswan at signetic dot ca
2007-09-20  0:46 ` [Bug preprocessor/33473] GCC does not correctly generate dependencies " pinskia at gcc dot gnu dot org
2007-09-20  1:11 ` rswan at signetic dot ca
2007-11-28 19:07 ` tromey 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=bug-33473-15111@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).