9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Matt H <matt@proweb.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] splitting the compiler
Date: Thu, 28 Feb 2002 09:42:06 +0000	[thread overview]
Message-ID: <20020228094206.7a0d0811.matt@proweb.co.uk> (raw)
In-Reply-To: <20020228090725.EBBF519AB8@mail.cse.psu.edu>


> many (i'd have said nearly all) of the worthwhile fancier global
> optimisations are perfectly portable, however much code they take to
> implement. 

As I said before, all of this concerns me for the future speed
imporvements on the next round of hardware. In the Itanium tech reviews
here :

http://www.extremetech.com/article/0,3396,s=1005&a=22477&app=7&ap=8,00.asp

it mentions :

"Intel's formally stated goal was to shift complexity out of the processor
logic and to the compiler. "

 From what I know of Intel it could well be conciously making this move as
part of it's destructive competitive instincts with regard to both AMD and
other compiler vendors.

This article :
http://www.open-mag.com/754088105111.htm

does a shoot out between Intel's C++ compiler and GCC, reporting that for
the OBLcpu benchmark suite Intel's compiler, on average, produced code
that ran 47% faster than GCC! (and sometimes 100% faster).

Intel's compiler, of course, made full use of SIMD instructions but,
significantly, showed a similar improvement over GCC when targetting
Athlons!

I'm glad 8c compiles quickly. Although I was disappointed the first time I
compiled a kernel. I went to make a cup of tea while it compiled only to
return for my cup and the bugger had already finished!

M


  reply	other threads:[~2002-02-28  9:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28  9:04 forsyth
2002-02-28  9:42 ` Matt H [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-28 17:21 forsyth
2002-02-27 15:32 paurea
2002-02-28 10:13 ` Thomas Bushnell, BSG
2002-02-28 16:02   ` ozan s yigit
2002-02-28 16:53     ` Thomas Bushnell, BSG
2002-03-04 10:03       ` ozan s. yigit
2002-03-04 17:04         ` Thomas Bushnell, BSG

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=20020228094206.7a0d0811.matt@proweb.co.uk \
    --to=matt@proweb.co.uk \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).