public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/9471] #pragma system_header vs. precompiled headers
Date: Fri, 29 Dec 2006 04:30:00 -0000	[thread overview]
Message-ID: <20061229043022.28341.qmail@sourceware.org> (raw)
In-Reply-To: <bug-9471-1920@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from tromey at gcc dot gnu dot org  2006-12-29 04:30 -------
I think this same problem will occur with #include_next
and #pragma once.  cpp doesn't currently seem to differentiate between
the PCH case and other kinds of preprocessing.


-- 

tromey at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at gcc dot gnu dot
                   |                            |org


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


       reply	other threads:[~2006-12-29  4:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9471-1920@http.gcc.gnu.org/bugzilla/>
2006-12-29  4:30 ` tromey at gcc dot gnu dot org [this message]
2008-11-28  7:48 ` geoffk at gcc dot gnu dot org
     [not found] <bug-9471-4@http.gcc.gnu.org/bugzilla/>
2023-11-14 22:55 ` cvs-commit at gcc dot gnu.org
2023-11-14 22:57 ` lhyatt at gcc dot gnu.org
2024-02-11 10:30 ` pinskia at gcc dot gnu.org
     [not found] <20030128034601.9471.bkoz@redhat.com>
2003-08-04  4:11 ` pinskia at physics dot uc dot edu
2003-08-23  1:32 ` dhazeghi at yahoo dot com
2003-12-19 10:09 ` pinskia at gcc dot gnu dot org
2004-06-09 20:18 ` geoffk 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=20061229043022.28341.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).