From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] NUMA
Date: Sun, 17 Jul 2011 14:04:45 +0200 [thread overview]
Message-ID: <201107171404.46042.dexen.devries@gmail.com> (raw)
In-Reply-To: <20110717100245.GA2352@polynum.com>
On Sunday 17 July 2011 12:02:45 tlaronde@polynum.com wrote:
> 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...).
optimizations make it more likely to trip over undefined behavior -- one that
`was-somehow-working' without it.
http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_14.html
http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_21.html
--
dexen deVries
> (...) I never use more than 800Mb of RAM. I am running Linux,
> a browser and a terminal.
rjbond3rd in http://news.ycombinator.com/item?id=2692529
next prev parent reply other threads:[~2011-07-17 12:04 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
2011-07-17 12:04 ` dexen deVries [this message]
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=201107171404.46042.dexen.devries@gmail.com \
--to=dexen.devries@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).