From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ken cc for linux
Date: Thu, 12 Mar 2015 15:23:32 +0000 [thread overview]
Message-ID: <CAOw7k5iJ4QG-gH=QBYSuHD8cc1vLF4XagTY+1OEfj54qFwhkNA@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5jV-Vdb0+KhADgGCLRS5AeHVGPnor6JqzXdJ4pDqntrtg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
On 12 March 2015 at 10:06, Charles Forsyth <charles.forsyth@gmail.com>
wrote:
> I've used it and lib9 in several other projects where other compilers
> couldn't be used for licensing reasons, or because they were awful.
>
I'll add that the compilers are great for kernel and other New World
systems work.
Once stable on a given platform, they've been quite robust (I never suspect
them at the start as a bug cause).
Code quality is rarely a bottleneck for systems work in my experience
(and there's a good reason that removing -O3 is a way to fix bugs with
other compilers).
If I were writing scientific computation, I wouldn't use C anyway, but if I
did, I'd worry
much more about the effectiveness of optimisation. For systems work? It's
really, really low on the list.
The cross-module type checking has also spotted a few things that every
other compiler missed.
Cross-compilation is easy and precise, with next to no configuration
required,
unlike nearly all the others; I rely on that a lot. It's worth the price of
entry for that alone, for me,
having suffered with gcc on an old OS project of mine; I'd never use it
again for anything new.
(Obviously I still use gcc for the 8 hour[!] Linux kernel compiles and
builds.)
lcc used to include all the code generators, so I suppose that would be
just as good, except
that it spits out assembly and you have to rely on external components,
which still leaves you cross when attempting
to cross-compile.
[-- Attachment #2: Type: text/html, Size: 2599 bytes --]
next prev parent reply other threads:[~2015-03-12 15:23 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 20:30 Aharon Robbins
2015-03-11 20:34 ` Aram Hăvărneanu
2015-03-11 21:04 ` Ryan Gonzalez
2015-03-11 21:54 ` Quintile
2015-03-11 23:04 ` Ryan Gonzalez
2015-03-11 23:19 ` Steve Simon
2015-03-12 6:39 ` arnold
2015-03-13 1:31 ` erik quanstrom
2015-03-13 13:24 ` Charles Forsyth
2015-03-13 17:59 ` Ryan Gonzalez
2015-03-13 18:19 ` Kurt H Maier
2015-03-19 15:35 ` Jeff Sickel
2015-03-19 16:09 ` [9fans] using git arnold
2015-03-19 16:22 ` Stanley Lieber
2015-03-19 16:34 ` Charles Forsyth
2015-03-19 16:36 ` Charles Forsyth
2015-03-19 16:39 ` Federico Benavento
2015-04-03 18:46 ` Jeff Sickel
2015-03-19 18:03 ` Skip Tavakkolian
2015-03-19 20:30 ` Jeff Sickel
2015-03-19 21:46 ` Skip Tavakkolian
2015-03-19 21:54 ` Devon H. O'Dell
2015-03-20 1:02 ` Kurt H Maier
2015-03-19 18:26 ` arnold
2015-03-28 11:14 ` Charles Forsyth
2015-03-28 14:00 ` Paul Lalonde
2015-03-30 9:48 ` Giacomo Tesio
2015-03-30 9:55 ` Giacomo Tesio
2015-03-30 16:16 ` Jeff Sickel
2015-03-30 19:47 ` Stanley Lieber
2015-03-30 20:41 ` Bakul Shah
2015-03-30 20:20 ` Giacomo Tesio
2015-03-30 20:32 ` Ryan Gonzalez
2015-03-31 3:17 ` arnold
2015-03-19 17:00 ` Jeff Sickel
2015-03-19 17:36 ` Ori Bernstein
2015-03-12 8:50 ` [9fans] ken cc for linux Aram Hăvărneanu
2015-03-12 17:53 ` Ryan Gonzalez
2015-03-12 8:51 ` Aram Hăvărneanu
2015-03-12 10:06 ` Charles Forsyth
2015-03-12 15:23 ` Charles Forsyth [this message]
2015-03-12 15:41 ` Brantley Coile
2015-03-12 17:14 ` Charles Forsyth
2015-03-13 1:28 ` erik quanstrom
2015-03-12 17:52 ` Ryan Gonzalez
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='CAOw7k5iJ4QG-gH=QBYSuHD8cc1vLF4XagTY+1OEfj54qFwhkNA@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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).