public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jengelh at inai dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/58283] Incorrect debug info when precompilation is on
Date: Mon, 02 Sep 2013 12:42:00 -0000 [thread overview]
Message-ID: <bug-58283-4-FO7prN07WX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58283-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58283
--- Comment #4 from Jan Engelhardt <jengelh at inai dot de> ---
>you cannot include a precompiled header from inside another header.
Ok. So, this limitation was properly implemented in gcc 4.7, which simply
skipped over the indirectly-included .gch file as if it did not exist. Safe
thing to do.
In gcc 4.8 however, the indirectly-included .gch *is* used rather than skipped,
which I base upon the observation that compile time goes down significantly for
projects with larger amounts of C++ code and the same indirect-inclusion
scheme.
next prev parent reply other threads:[~2013-09-02 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 16:02 [Bug c/58283] New: " jengelh at inai dot de
2013-09-02 11:17 ` [Bug c/58283] " rguenth at gcc dot gnu.org
2013-09-02 11:46 ` jengelh at inai dot de
2013-09-02 12:42 ` jengelh at inai dot de [this message]
2013-09-02 12:51 ` rguenth at gcc dot gnu.org
2013-09-02 19:54 ` jengelh at inai dot de
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-58283-4-FO7prN07WX@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).