From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] caveat... optimizer? the `zero and forget' thread on HN
Date: Mon, 29 Oct 2012 19:36:16 -0400 [thread overview]
Message-ID: <74f73b64cc6de4a3bd10367591439816@kw.quanstro.net> (raw)
In-Reply-To: <20121029232652.5160BB827@mail.bitblocks.com>
> No disagreement there on "requiring" optimization. But my
> point was that a programmer should understand the standard
> rather than complain when he gets "surprised" due to his lack
> of knowledge.
i agree that one should know the language. but i'm not sure i'll
say it's the programmer's fault when the compiler does things to
the programmer. that to me goes a bit too far.
> /sys/src/cmd follows plan9 c, not c99, right? But pick a
> similar set of programs. If this happens, I claim it would be
> because programs assume something not guaranteed by the
> compiler.
and i can design a standards-compatable compiler that will break
most any c program.
this is similar to saying that i can design a namespace that will
break almost any plan 9 program.
what i think has broken down is common sense among compiler
writers. they're too focused on being fast, and not focused enough
on being *useful*.
> > > > it goes without saying, i think a compiler that largely does what you
> > > > ask it to optimizes the scarce resource: developer time.
> > >
> > > That is a separate issue.
> >
> > actually, i think it *is* the issue.
>
> Best way to save developer time is to program in a HLL and not
> worry about bit fiddling. C is not a HLL.
this is a spurious argument, since we are in fact talking about c.
- erik
next prev parent reply other threads:[~2012-10-29 23:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 9:45 dexen deVries
2012-10-29 10:12 ` tlaronde
2012-10-29 13:43 ` erik quanstrom
2012-10-29 13:35 ` erik quanstrom
2012-10-29 22:35 ` Bakul Shah
2012-10-29 22:47 ` Charles Forsyth
2012-10-29 23:05 ` Bakul Shah
2012-10-29 23:07 ` erik quanstrom
2012-10-29 23:15 ` David Leimbach
2012-10-29 23:20 ` erik quanstrom
2012-10-29 23:53 ` andrey mirtchovski
2012-10-29 23:59 ` Kurt H Maier
2012-10-29 23:10 ` erik quanstrom
2012-10-29 23:26 ` Bakul Shah
2012-10-29 23:31 ` Bakul Shah
2012-10-29 23:36 ` erik quanstrom [this message]
2012-10-29 23:58 ` Charles Forsyth
2012-10-30 0:52 ` Bakul Shah
2012-10-30 1:01 ` erik quanstrom
2012-10-30 7:55 ` tlaronde
2012-10-30 0:35 ` Bakul Shah
2012-10-30 1:10 ` erik quanstrom
2012-10-30 3:06 ` Bakul Shah
2012-10-30 3:16 ` Corey Thomasson
2012-10-30 13:08 ` erik quanstrom
2012-10-30 15:15 ` arnold
2012-10-30 1:46 ` cinap_lenrek
2012-10-30 1:21 ` Kurt H Maier
2012-10-30 8:07 ` tlaronde
2012-10-30 10:26 ` Richard Miller
2012-10-30 10:39 ` dexen deVries
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=74f73b64cc6de4a3bd10367591439816@kw.quanstro.net \
--to=quanstro@quanstro.net \
--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).