public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Benjamin Kosnik <bkoz@redhat.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Suggestions for improving gcc 3.2 compilation speed?
Date: Sat, 08 Mar 2003 22:17:00 -0000	[thread overview]
Message-ID: <20030308151257.3b62b1ae.bkoz@redhat.com> (raw)
In-Reply-To: <jm65qtsixy.fsf@desire.geoffk.org>


>> Is the .pch just not being used?
>
>It's possible. 

I'm hoping that it's not being used, just from the timings.

I was hoping for a bit more info than this if possible. Like, should the
.pch file show up in -v -H? How is this debugged?

>You might want to check whether you're using a compiler that uses .pch
>or .gch as the PCH extension.

Apparently, mainline g++ on linux uses .pch by default. I tried to just
generate a pch as you've previously instructed and the output file has
.pch, not .gch. 

Perhaps you could try this yourself?

>Also, consider using the -Winvalid-pch flag.

Ummmm, yeah. Done and done. 

On mainline gcc, you can generate a precompiled C++ include for
libstdc++-v3 with relatively small effort. To recap:

cd bld/target/libstdc++-v3/include
make stamp-std-precompile

Also, at the suggestion of Mike Stump, I re-did the C++ includes to
first include stdc++.h. Then, I generated a stdc++.h.pch. That approach,
which is only a stylistic variation, can be found here:

http://gcc.gnu.org/ml/gcc-patches/2003-03/msg00694.html

I'm not quite sure what to do now.

-benjamin

  reply	other threads:[~2003-03-08 21:13 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 19:19 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 [this message]
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               ` pch messages Zack Weinberg
     [not found] <200303071624.13957.garen@wsu.edu>
2003-03-10 15:14 ` Suggestions for improving gcc 3.2 compilation speed? Anna Fowles-Winkler
  -- strict thread matches above, loose matches on Subject: below --
2003-02-27 23:50 Anna Fowles-Winkler
2003-02-28  0:02 ` Matt Austern
2003-02-28  7:25 ` Kaveh R. Ghazi
2003-02-28 15:16   ` Joel Sherrill
2003-03-03 17:25     ` Anna Fowles-Winkler
2003-03-07  1:55   ` Anna Fowles-Winkler
2003-03-07  2:52     ` Russell Shaw
2003-03-07 11:15       ` Lars Segerlund
2003-03-07 11:19         ` Biagio Lucini
2003-03-07 11:25           ` Karel Gardas
2003-03-07 19:39             ` tm_gccmail
2003-03-07 12:18           ` Lars Segerlund
2003-03-07 12:24           ` Lars Segerlund
2003-03-07 14:07             ` Michael S. Zick
2003-03-07 19:12           ` Mike Stump
2003-03-07 19:41             ` Zack Weinberg
2003-03-07 19:53               ` Mike Stump
2003-03-07 20:51             ` Karel Gardas
2003-03-08  0:19               ` Mike Stump
2003-03-07 13:33         ` Russell Shaw
2003-03-07  4:01     ` Kaveh R. Ghazi
2003-03-07 18:30       ` Anna Fowles-Winkler
2003-03-07 20:57       ` Anna Fowles-Winkler
2003-03-07 22:50         ` Kaveh R. Ghazi
2003-03-07 23:02           ` Geoff Keating
2003-03-10 15:20           ` Anna Fowles-Winkler
2003-03-15  1:45             ` Kaveh R. Ghazi
2003-03-15  7:16               ` Zack Weinberg
2003-03-15 15:54                 ` Kaveh R. Ghazi
2003-03-17 16:39                 ` Michael Matz

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=20030308151257.3b62b1ae.bkoz@redhat.com \
    --to=bkoz@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@geoffk.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).