public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Geoff Keating <geoffk@geoffk.org>
To: amep@softhome.net
Cc: gcc@gcc.gnu.org
Subject: Re: Precompiled headers (or other speed ups)
Date: Mon, 08 Jan 2001 21:00:00 -0000	[thread overview]
Message-ID: <jm8zol1fsh.fsf@geoffk.org> (raw)
In-Reply-To: <20010108214448B.amp@tiny>

amep@softhome.net writes:

> I was wondering if there is anyone actively working on precompiled
> headers (my program is a good candidate for this) or something else to
> speed up the compilation? If so, I'd love help out by testing or doing
> anything else I can?

Yes, I'm actively working on precompiled headers.  They've been
delayed a bit to allow for the GCC 3.0 release to get out the door,
but they should be in 3.1.

-- 
- Geoffrey Keating <geoffk@geoffk.org>

  reply	other threads:[~2001-01-08 21:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <978997896.4164.ezmlm@gcc.gnu.org>
2001-01-08 19:45 ` amep
2001-01-08 21:00   ` Geoff Keating [this message]
2001-01-09  0:41     ` Adrien Hernot
2001-01-08 20:41 dewar
2001-01-09  3:01 ` Rob Taylor
2001-01-09 10:04 ` amep
2001-01-09 14:36 ` Stan Shebs
2001-01-08 21:09 dewar
2001-01-09  0:33 ` Geoff Keating
2001-01-09 11:26 dewar
2001-01-09 14:55 dewar
2001-01-09 15:43 ` Stan Shebs
2001-01-10 22:55   ` Toon Moene
2001-01-10  5:29 ` Andi Kleen
2001-01-10  8:32   ` Phil Edwards
2001-01-10 15:12   ` Stan Shebs
2001-01-09 19:52 dewar
2001-01-10  8:50 dewar
2001-01-10  9:02 Phil Edwards
2001-01-10  9:11 David Korn
2001-01-10  9:29 dewar
2001-01-10  9:35 dewar
2001-01-10 18:53 ` Yu Xuanwei
2001-01-10  9:56 David Korn
2001-01-10 11:14 ` Zack Weinberg
2001-01-10 13:54   ` Neil Booth
2001-01-10 15:45     ` Zack Weinberg
2001-01-10 15:26   ` Joe Buck
2001-01-10 10:21 dewar
2001-01-10 11:45 dewar

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=jm8zol1fsh.fsf@geoffk.org \
    --to=geoffk@geoffk.org \
    --cc=amep@softhome.net \
    --cc=gcc@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).