9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] NUMA
Date: Sun, 17 Jul 2011 12:02:45 +0200	[thread overview]
Message-ID: <20110717100245.GA2352@polynum.com> (raw)
In-Reply-To: <20110717084411.95552B827@mail.bitblocks.com>

On Sun, Jul 17, 2011 at 01:44:11AM -0700, Bakul Shah wrote:
> On Sun, 17 Jul 2011 09:38:47 +0200 tlaronde@polynum.com  wrote:
> >
> > Furthermore, I don't know for others, but I prefer correctness over
> > speed. I mean, if a program is proved to be correct (and very few are),
> > complex acrobatics from the compiler, namely in the "optimization" area,
> > able to wreak havoc all the code assumptions, is something I don't buy.
>
> C's design has compromises in favor of speed to correctness
> (mainly by underspecifying, by leaving more things upto the
> implementor). So if you really prefer correctness over speed,
> you should be using Scheme, ML or Haskell etc but not C!

Yes and no. IMHO one of the greatest strengths of C is that the language
is small (standard lib is apart) and its description short and to the
point. K&R and, at least, ANSI C were short and if there are subtleties
(promotions... signed/unsigned etc.), knowing what is guaranteed
and what is not can be achieved. (And C is a general purpose
language, but not an all purposes language [standard C]: calculus
is not its realm, since even integer overflow is unspecified.)

My woe is more that an optimization can say "this may improve speed (or
may not, even slow down processing...)": OK. But an optimization
that can break a program, that is an optimization whose correctness
is not guaranteed, is something I can't understand why it is even
proposed (since I fail to see why someone would be happy to have
more rapidly an incorrect result, that can even not be said to be close
to the correct one for some epsilon...).

>[...]
> Also note that the ISA implementations these days are quite
> complex (perhaps even more than your typical program).  We
> don't see this complexty because it is all hidden behind a
> relatively simple ISA.  But remember the FOOF bug? Usually the
> vendor has a long errata list (typically only available on a
> need to know basis and only under NDA!). And usually they
> don't formally prove the implementation right; they just run
> zillions of test vectors! I bet you would be scandalized if
> you knew what they do :-)

Scandalized, perhaps... surprised: not! Because stating explicitely
the domain of definition of operations on not integer, not scaled
and certainly not "reals" is not trivial at all precisely by lack
of uniformity, specially on a higher level when you consider not
one manipulation, but a sequence... And the the decreasing size of
the hardware components will lead to impredictability by design!

>[...]
> I seriously think you will be happier with Scheme!

That's on my TODO list. Since a long time now... ;)
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C




  reply	other threads:[~2011-07-17 10:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15 15:15 tlaronde
2011-07-15 20:21 ` tlaronde
2011-07-15 20:47   ` ron minnich
2011-07-15 22:59     ` Charles Forsyth
2011-07-16  8:02     ` tlaronde
2011-07-16 16:27       ` erik quanstrom
2011-07-16 18:06         ` tlaronde
2011-07-16 19:29           ` Ethan Grammatikidis
2011-07-16 19:54           ` erik quanstrom
2011-07-16 20:56             ` dexen deVries
2011-07-16 22:10               ` Charles Forsyth
2011-07-17  1:44                 ` erik quanstrom
2011-07-17  7:38                   ` tlaronde
2011-07-17  8:44                     ` Bakul Shah
2011-07-17 10:02                       ` tlaronde [this message]
2011-07-17 12:04                         ` dexen deVries
2011-07-17 15:24                       ` erik quanstrom
2011-07-17 15:28                         ` ron minnich
     [not found]                         ` <CAP6exYL2DJXbKfPZ8+D5uL=fRWKEyr8vY2OVc4NTO3wsFo=Unw@mail.gmail.c>
2011-07-17 15:32                           ` erik quanstrom
2011-07-17 17:16                         ` Bakul Shah
2011-07-17 17:21                           ` erik quanstrom
2011-07-17 15:51                     ` erik quanstrom
2011-07-17 16:12                       ` dexen deVries
2011-07-17 16:37                       ` tlaronde
2011-07-17 10:08               ` Ethan Grammatikidis
2011-07-17 14:50                 ` erik quanstrom
2011-07-17 17:01                   ` Ethan Grammatikidis
2011-07-17  3:39       ` Joel C. Salomon
2011-07-17  7:01         ` tlaronde
2011-07-17 15:05           ` Joel C. Salomon
2011-07-17 15:26           ` erik quanstrom
2011-07-17 15:52             ` ComeauAt9Fans@gmail.com

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=20110717100245.GA2352@polynum.com \
    --to=tlaronde@polynum.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).