public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Tim Prince" <tprince@computer.org>
To: "Matthias Kurz" <mk@baerlap.north.de>,
	"Erik Mouw" <J.A.K.Mouw@its.tudelft.nl>
Cc: <gcc@gcc.gnu.org>
Subject: Re: best optimization under IRIX ?
Date: Wed, 06 Sep 2000 20:28:00 -0000	[thread overview]
Message-ID: <004c01c0187b$ffd3d290$756e8ad1@timayum4srqln4> (raw)
In-Reply-To: <20000906162002.B2239@baerlap.north.de>

----- Original Message -----
From: "Matthias Kurz" <mk@baerlap.north.de>
To: "Erik Mouw" <J.A.K.Mouw@its.tudelft.nl>
Cc: <gcc@gcc.gnu.org>
Sent: Wednesday, September 06, 2000 7:20 AM
Subject: Re: best optimization under IRIX ?


> The cc code runs twice as fast on a R12000, again (did not try gcc,
> i guess it will be also twice as fast). But then, the R12000/300 has 8MB
> cache, while the R10000/180 has only 1MB.

I saw some cases where gcc ran somewhat better relative to MipsPro cc on the
r12k than on the r10k, just enough so to support the claim that r12k had
corrected some bottlenecks.  8MB cache?  Your problem will have to sit a
long time on a single processor to take advantage of that.  The r12k box I
had access to had 4MB L2 cache, and my processes were interrupted far too
often to take advantage of that.  Funny thing, my laptop does as well on
Livermore Kernels as that r12k did.  What a difference a year or two can
make.
>


  reply	other threads:[~2000-09-06 20:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-05 20:26 Matthias Kurz
2000-09-05 23:36 ` Tim Prince
2000-09-06  6:16   ` Matthias Kurz
2000-09-06  3:17 ` Erik Mouw
2000-09-06  7:26   ` Matthias Kurz
2000-09-06 20:28     ` Tim Prince [this message]
2000-09-07  4:56       ` Matthias Kurz
2000-09-07  5:47         ` Matthias Kurz

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='004c01c0187b$ffd3d290$756e8ad1@timayum4srqln4' \
    --to=tprince@computer.org \
    --cc=J.A.K.Mouw@its.tudelft.nl \
    --cc=gcc@gcc.gnu.org \
    --cc=mk@baerlap.north.de \
    /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).