public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olafvdspek at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/47857] Pragma once warning when compiling PCH
Date: Thu, 15 Dec 2011 10:47:00 -0000 [thread overview]
Message-ID: <bug-47857-4-dbB4sGLYtx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47857-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47857
Olaf van der Spek <olafvdspek at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--- Comment #2 from Olaf van der Spek <olafvdspek at gmail dot com> 2011-12-15 10:41:07 UTC ---
(In reply to comment #1)
> Dup of bug 39029 which shows the warning is just part of the symptom.
>
> *** This bug has been marked as a duplicate of bug 39029 ***
It's *not* a duplicate. This one is about generating the .gch.
The other one is about using the .gch (and not about the warning message).
next prev parent reply other threads:[~2011-12-15 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 12:32 [Bug preprocessor/47857] New: " olafvdspek at gmail dot com
2011-12-15 2:15 ` [Bug preprocessor/47857] " pinskia at gcc dot gnu.org
2011-12-15 10:47 ` olafvdspek at gmail dot com [this message]
2011-12-15 13:40 ` redi at gcc dot gnu.org
2012-04-28 14:40 ` olafvdspek at gmail dot com
2013-10-03 17:42 ` ripzonetriton at gmail dot com
2015-01-07 0:25 ` p_hampson at wargaming dot net
2023-08-24 8:31 ` [Bug pch/47857] " egallager at gcc dot gnu.org
2023-11-14 22:55 ` cvs-commit at gcc dot gnu.org
2023-11-14 22:58 ` lhyatt at gcc dot gnu.org
2024-02-11 10:29 ` 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-47857-4-dbB4sGLYtx@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).