public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: Mike Stump <mrs@apple.com>,
	 Karel Gardas <kgardas@objectsecurity.com>,
	bkoz@redhat.com,  gcc@gcc.gnu.org
Subject: Re: pch messages
Date: Tue, 11 Mar 2003 01:39:00 -0000	[thread overview]
Message-ID: <871y1eadj7.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <jmu1eapuym.fsf@desire.geoffk.org> (Geoff Keating's message of "10 Mar 2003 17:12:33 -0800")

Geoff Keating <geoffk@geoffk.org> writes:

> Someone (maybe even bkoz) suggested that -H should provide this
> information; that certainly sounds like the right place to have
> debugging info for header-inclusion problems.

Agree.  Patches are welcome.  (If we do this, we should make -H more
prominently documented.)

zw

      reply	other threads:[~2003-03-11  1:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 19:19 Suggestions for improving gcc 3.2 compilation speed? Benjamin Kosnik
2003-03-07 21:22 ` Karel Gardas
2003-03-07 22:08   ` Geoff Keating
2003-03-07 23:35 ` Mike Stump
2003-03-07 23:55   ` Devang Patel
2003-03-08  1:46   ` Benjamin Kosnik
2003-03-08  2:00   ` Geoff Keating
2003-03-08 11:21   ` Benjamin Kosnik
2003-03-08 21:01     ` Geoff Keating
2003-03-08 22:17       ` Benjamin Kosnik
2003-03-08 22:57         ` Geoff Keating
2003-03-09 22:30           ` Benjamin Kosnik
2003-03-10 18:34     ` Mike Stump
2003-03-10 18:47       ` pch messages [was: Re: Suggestions for improving gcc 3.2 compilation speed?] Karel Gardas
2003-03-11  0:47         ` B. Kosnik
2003-03-11  0:53           ` Mike Stump
2003-03-11  1:38             ` Geoff Keating
2003-03-11  1:39               ` Zack Weinberg [this message]

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=871y1eadj7.fsf@egil.codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=bkoz@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@geoffk.org \
    --cc=kgardas@objectsecurity.com \
    --cc=mrs@apple.com \
    /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).