From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Is Plan 9 C "Less Dangerous?"
Date: Mon, 3 Sep 2018 02:03:37 +0100 [thread overview]
Message-ID: <CAOw7k5iBi6PGdrSwASFAN=mu-mYrxzjYW34NTM6NcEe6xFH8Yg@mail.gmail.com> (raw)
In-Reply-To: <807fabbc-e97a-4e60-1562-a126dd79008a@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
The Plan 9 C compiler doesn't take an insane view of the meaning of
"undefined behaviour", which makes a big difference.
It also assumes you know how to write loops if they need to be fast (which
frankly hasn't really mattered at the O/S level, esp on modern hardware),
so it won't "optimise" essential code out of your program by miscalculating
the ranges during "aggressive-loop-optimisation".
No doubt it could be better, but it could easily be worse.
The executable is also finite size, not unbounded-but-finite.
For a compiler of a language the size and complexity of C (without some
ANSI crud), I think it's not far off a size comparable to the language
complexity
(although it could be a bit smaller); meanwhile, by treating "compiling C"
as a subset problem of "compiling C++", gcc and especially clang are vast
whales whistling at the wrong frequency for the problem.
On Sun, 2 Sep 2018 at 20:23, Iruatã Souza <iru.muzgo@gmail.com> wrote:
> On 09/02/2018 09:31 AM, Chris McGee wrote:
> > I'm curious what
> > tools are available to help discover bugs.
> >
>
> Does simplicity and clarity count?
>
>
[-- Attachment #2: Type: text/html, Size: 1513 bytes --]
next prev parent reply other threads:[~2018-09-03 1:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 16:31 Chris McGee
2018-09-02 16:52 ` hiro
2018-09-03 4:07 ` Lucio De Re
2018-09-03 12:40 ` Chris McGee
2018-09-03 17:58 ` Ethan Gardener
2018-09-04 10:51 ` Lucio De Re
2018-09-04 11:33 ` Ethan Gardener
2018-09-04 11:41 ` Chris McGee
2018-09-02 18:16 ` Lucio De Re
2018-09-02 19:18 ` Steve Simon
2018-09-02 19:21 ` Iruatã Souza
2018-09-03 1:03 ` Charles Forsyth [this message]
2018-09-03 2:03 ` Skip Tavakkolian
2018-09-04 23:17 ` Charles Forsyth
2018-09-04 23:30 ` Tyga
2018-09-05 2:29 ` Chris McGee
2018-09-05 11:23 ` Dave MacFarlane
2018-09-05 11:42 ` Chris McGee
2018-09-05 13:35 ` Ethan Gardener
2018-09-05 15:38 ` Iruatã Souza
2018-09-05 23:59 ` Chris McGee
2018-09-06 0:32 ` Bakul Shah
2018-09-06 3:40 ` Lucio De Re
2018-09-06 11:41 ` Chris McGee
2018-09-06 13:37 ` Ethan Gardener
2018-09-06 17:48 ` Richard Miller
2018-09-06 19:08 ` Skip Tavakkolian
2018-09-06 21:21 ` Chris McGee
2018-09-07 8:32 ` Richard Miller
2018-09-05 3:25 ` Ori Bernstein
2018-09-05 8:19 ` Ethan Gardener
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='CAOw7k5iBi6PGdrSwASFAN=mu-mYrxzjYW34NTM6NcEe6xFH8Yg@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).