From: Zack Weinberg <zack@codesourcery.com>
To: "John S. Dyson" <toor@y.jdyson.com>
Cc: diep@xs4all.nl (Vincent Diepeveen),
gcc@gcc.gnu.org (gcc@gcc.gnu.org List)
Subject: Re: gcc and compiling speed
Date: Mon, 01 Mar 2004 05:31:00 -0000 [thread overview]
Message-ID: <871xodqgjx.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <200403010500.i2150gBA080486@y.jdyson.com.> (John S. Dyson's message of "Mon, 1 Mar 2004 00:00:42 -0500 (EST)")
"John S. Dyson" <toor@y.jdyson.com> writes:
>>
>> btw At multiprocessor BSD machines, does gcc get run using all processors
>> there instead of running all threads at 1 processor? If not, i know
>> something to speed you up quite some...
>>
> FreeBSD has a couple of multi-threading libs, and at least one
> of them allows for multi-cpu threading. Frankly, I don't keep
> up with the official release versions, but I often use the
> multi-cpu threading libs.
GCC itself is single threaded, but Make has the wonderful -j option
which lets you parallelize entire builds.
zw
next prev parent reply other threads:[~2004-03-01 5:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 4:23 Vincent Diepeveen
2004-03-01 5:00 ` John S. Dyson
2004-03-01 5:31 ` Zack Weinberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-01 0:43 Andrew Pinski
2004-03-01 2:58 ` Theo de Raadt
2004-03-01 3:07 ` Daniel Jacobowitz
2004-03-01 3:46 ` Theo de Raadt
2004-03-01 3:55 ` Gabriel Dos Reis
2004-03-01 3:59 ` Theo de Raadt
2004-03-01 4:15 ` Daniel Berlin
2004-03-14 22:15 ` Gerald Pfeifer
2004-03-01 6:00 ` Andreas Jaeger
2004-03-01 19:40 ` Peter Galbavy
2004-03-01 19:51 ` Andreas Jaeger
2004-03-01 20:05 ` Peter Galbavy
2004-03-01 20:15 ` William Ahern
2004-03-01 3:10 ` Zack Weinberg
2004-03-01 3:49 ` Theo de Raadt
2004-03-01 4:00 ` Eric Christopher
2004-03-01 4:05 ` Theo de Raadt
2004-03-01 4:11 ` Eric Christopher
2004-03-01 4:00 ` Gabriel Dos Reis
2004-03-01 4:01 ` Zack Weinberg
[not found] ` <20040301071403.GA8953@tetto.gentiane.org>
2004-03-01 7:27 ` Zack Weinberg
2004-03-01 8:09 ` Steven Bosscher
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=871xodqgjx.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=diep@xs4all.nl \
--cc=gcc@gcc.gnu.org \
--cc=toor@y.jdyson.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).