9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] fast compilers
Date: Fri,  4 Apr 2003 15:21:02 -0700	[thread overview]
Message-ID: <Pine.LNX.4.44.0304041518190.24389-100000@fbsd.cpsc.ucalgary.ca> (raw)

I know theo de raadt is a controversial person, but i found this post of his
interesting:

http://www.netsys.com/openbsd-tech/2003/02/msg00064.html

to quote:

> > gcc 3.2.1 is TWICE AS SLOW as gcc 2.95, and the more recent development
> > are
> > even SLOWER.
>
> What is making successive versions of GCC slower?

I'm not exactly sure.  My theory would be that in their zeal for
trying to get gcc to catch up to commercial compilers in quality of
output, they have paid much less attention to ensuring the compiler
itself is fast.

Sigh.

I wish the plan9 compiler was 100% free.  It's blazingly fast.

And as a developer, I want a fast compiler more than I want fast output.



             reply	other threads:[~2003-04-04 22:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04 22:21 andrey mirtchovski [this message]
2003-04-04 23:02 ` Andrew
2003-04-04 23:07   ` jkw
2003-04-05  0:14     ` Andrew
2003-04-05  0:28       ` William Josephson
2003-04-05  0:31         ` Andrew
2003-04-05  0:59           ` Dan Cross
2003-04-05  1:41             ` Andrew
2003-04-05  1:47               ` Dan Cross
2003-04-05  1:48                 ` David Presotto
2003-04-07  9:06     ` Robin KAY
2003-04-07 17:10 rog
     [not found] <bd525c545ba7fe2d9c6641953a77c609@vitanuova.com>
2003-04-07 18:50 ` Theo de Raadt
2003-04-08  6:05   ` Dan Cross
2003-04-08  6:07     ` Dan Cross
2003-04-08  6:11     ` Scott Schwartz
2003-04-08  6:12       ` Charles Forsyth
2003-04-08 10:28         ` bwc
2003-04-08 10:46           ` Charles Forsyth
2003-04-08  6:14       ` Dan Cross

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=Pine.LNX.4.44.0304041518190.24389-100000@fbsd.cpsc.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).