public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: speleganSpAmNoTmE@csc.com (Stewart Pelegan)
To: help-gcc@gnu.org
Subject: Multi-processor Switch for Compiling and Linking
Date: Wed, 03 Nov 1999 11:03:00 -0000	[thread overview]
Message-ID: <YZhdJSdSjdz4-pn2-qhdqVhdXQuq8@cscr3202> (raw)

Is there a switch that can be used to tell either gcc or g++ to take
advantage of your multiprocessor environment?

I've got an UltraSPARC 10 and an UltraSPARC 60.  The Ultra10 has 128MB of RAM 
and one processor and the Ultra60 has 512MB and two processors.
Compiling and linking code seems to take about the same amount of time
on both boxes.  Is there anything I can do on the Ultra60 to speed up compiling
and linking?  Thanks.

Stewart Pelegan <spelegan@csc.com>
Computer Sciences Corporation
301.921.3206
Fax: 301.840.8934

WARNING: multiple messages have this Message-ID

From: speleganSpAmNoTmE@csc.com (Stewart Pelegan)
To: help-gcc@gnu.org
Subject: Multi-processor Switch for Compiling and Linking
Date: Tue, 30 Nov 1999 23:28:00 -0000	[thread overview]
Message-ID: <YZhdJSdSjdz4-pn2-qhdqVhdXQuq8@cscr3202> (raw)
Message-ID: <19991130232800.SNad6TdjO0wIaLSuwJ3Lk8mnyekenJjXpfVVS22Y_BQ@z> (raw)

Is there a switch that can be used to tell either gcc or g++ to take
advantage of your multiprocessor environment?

I've got an UltraSPARC 10 and an UltraSPARC 60.  The Ultra10 has 128MB of RAM 
and one processor and the Ultra60 has 512MB and two processors.
Compiling and linking code seems to take about the same amount of time
on both boxes.  Is there anything I can do on the Ultra60 to speed up compiling
and linking?  Thanks.

Stewart Pelegan <spelegan@csc.com>
Computer Sciences Corporation
301.921.3206
Fax: 301.840.8934

             reply	other threads:[~1999-11-03 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-03 11:03 Stewart Pelegan [this message]
1999-11-04  1:18 ` Joerg Faschingbauer
1999-11-30 23:28   ` Joerg Faschingbauer
1999-11-30 23:28 ` Stewart Pelegan

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=YZhdJSdSjdz4-pn2-qhdqVhdXQuq8@cscr3202 \
    --to=speleganspamnotme@csc.com \
    --cc=help-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).