public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kristiaan dot lenaerts at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/14933] missing pre-compiled header depends with -MD
Date: Fri, 04 Jun 2010 20:11:00 -0000 [thread overview]
Message-ID: <20100604201045.2161.qmail@sourceware.org> (raw)
In-Reply-To: <bug-14933-8321@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from kristiaan dot lenaerts at gmail dot com 2010-06-04 20:10 -------
Created an attachment (id=20847)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20847&action=view)
Updated fix for improper PCH dependency tracking
I got hit by this bug a few weeks ago when working on a C++ project. This
project has a setup for which using -fpch-deps will not work, most pch files
include local headers that have to be referenced by their complete path
elsewhere.
I rebased the proposed fix from Mario on the 4.5 branch (I created it when 4.5
was not yet out). I'm using this patch for about a month now without any
obvious problems, but I would like to get this in mainline.
What are the steps that I should take? I have not yet run the testsuite. (this
is on a corporate laptop running under cygwin - windows XP and full
hd-encryption - so compiling gcc was painfull, and I imagine running the
testsuite will be worse)
Would it be ok if I run the testsuite on cygwin with and without the patch, and
if the results are the same submit this patch to gcc-patches (with meaningfull
changelog entry)? I could also test on a x64_64-pc-linux-gnu machine at home,
but it could take a while before I can test there.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14933
next prev parent reply other threads:[~2010-06-04 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14933-8321@http.gcc.gnu.org/bugzilla/>
2006-03-20 19:40 ` pedz at easesoftware dot net
2006-07-25 15:23 ` mjuric at astro dot princeton dot edu
2007-01-27 20:03 ` tromey at gcc dot gnu dot org
2007-11-28 19:07 ` tromey at gcc dot gnu dot org
2008-03-14 21:26 ` tromey at gcc dot gnu dot org
2008-04-20 19:00 ` tromey at gcc dot gnu dot org
2008-04-20 23:56 ` pedz at easesoftware dot com
2008-11-03 22:35 ` pinskia at gcc dot gnu dot org
2010-06-04 20:11 ` kristiaan dot lenaerts at gmail dot com [this message]
2004-04-13 4:21 [Bug c/14933] New: " dfries at mail dot win dot org
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=20100604201045.2161.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: 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).