public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfries at mail dot win dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/14933] New: missing pre-compiled header depends with -MD
Date: Tue, 13 Apr 2004 04:21:00 -0000	[thread overview]
Message-ID: <20040413041446.14933.dfries@mail.win.org> (raw)

When using a pre-compiled header the option -MD produces no
dependencies on the pre-compiled header or the headers that the
pre-compiled header is composed of.  I would expect the same problem
on any of the dependency generating options.

SpacedOut:/tmp/test$ gcc -MD headers.h  -o headers.h.gch
SpacedOut:/tmp/test$ cat headers.h.d 
headers.h.gch: headers.h

> so far so good

SpacedOut:/tmp/test$ gcc -MD main.c -o main 
SpacedOut:/tmp/test$ cat main.d
main: main.c

> So main doesn't require anything?  I don't think so.

SpacedOut:/tmp/test$ rm -f *.d *.i *.s a.out *.gch main
SpacedOut:/tmp/test$ gcc -MD main.c -o main 
SpacedOut:/tmp/test$ cat main.d
main: main.c headers.h

> Much better.  I would think it should be the following when using
> the precompiled headers.
main: main.c headers.h.gch

SpacedOut:/tmp/test$ gcc -v
Reading specs from /home/david/WorkProjects/OpenSceneGraph/DevelGcc/install/lib/gcc/i686-pc-linux-gnu/3.5.0/specs
Configured with: ../gcc_src/configure --enable-languages=c++ --prefix=/home/david/WorkProjects/OpenSceneGraph/DevelGcc/install 
--exec-prefix=/home/david/WorkProjects/OpenSceneGraph/DevelGcc/install
Thread model: posix
gcc version 3.5.0 20040412 (experimental)


header.h:
#ifndef _HEADERS_H
#define _HEADERS_H 1
const int value=32;
#endif /* _HEADERS_H */

main.c:
#include "headers.h"

int main(int argc, char ** argv)
{
        return value;
}

-- 
           Summary: missing pre-compiled header depends with -MD
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dfries at mail dot win dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i386-linux
  GCC host triplet: i386-linux
GCC target triplet: i386-linux


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


             reply	other threads:[~2004-04-13  4:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13  4:21 dfries at mail dot win dot org [this message]
2004-04-13  4:27 ` [Bug pch/14933] " pinskia at gcc dot gnu dot org
2004-04-13 19:01 ` geoffk at gcc dot gnu dot org
2004-04-17  8:43 ` geoffk at gcc dot gnu dot org
2004-12-14 13:19 ` 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=20040413041446.14933.dfries@mail.win.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: 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).