From: Pavel Shevaev <pacha.shevaev@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Precompiled headers issue: -c and -fpch-preprocess should be used together?
Date: Mon, 19 Apr 2010 17:51:00 -0000 [thread overview]
Message-ID: <n2qd9c3f61a1004190422n911043fh13f57c5d6309a18@mail.gmail.com> (raw)
In-Reply-To: <mcr633qex03.fsf@dhcp-172-17-9-151.mtv.corp.google.com>
> It's kind of special purpose and I think it would fit better on
> http://gcc.gnu.org/wiki/FAQ . Want to add an entry?
I'll give it a try :)
--
Best regards, Pavel
prev parent reply other threads:[~2010-04-19 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 7:57 Pavel Shevaev
2010-04-07 14:36 ` Ian Lance Taylor
2010-04-16 20:59 ` Pavel Shevaev
2010-04-17 3:23 ` Ian Lance Taylor
2010-04-19 17:51 ` Pavel Shevaev [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=n2qd9c3f61a1004190422n911043fh13f57c5d6309a18@mail.gmail.com \
--to=pacha.shevaev@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).