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:10:55 -0400 [thread overview]
Message-ID: <0f05642b113b3ecfc160e82a9ca4db32@brasstown.quanstro.net> (raw)
In-Reply-To: <20121029223541.8C198B827@mail.bitblocks.com>
On Mon Oct 29 18:37:11 EDT 2012, bakul@bitblocks.com wrote:
> On Mon, 29 Oct 2012 09:35:00 EDT erik quanstrom <quanstro@quanstro.net> wrote:
> > On Mon Oct 29 05:47:10 EDT 2012, dexen.devries@gmail.com wrote:
> > > http://news.ycombinator.com/item?id=4711346
> > >
> > > 9fans says, ``no room in the compiler world for amateurs''. what's your tak
> > e
> > > on the above fubar?
> >
> > any sort of "advanced" code-moving optimization is confusing. but the
> > way c/c++ are used in linux, bsd & osx, there is a noticable benefit to
> > optimizing calls away. it takes smarts to optimize away those recursive
> > wrapper macros. so they're in a bit of a pickle.
>
> It has nothing to do with "how" C/C++ are used in linux, bsd &
> osx -- you forgot windows! The C standard allows a lot of
> leeway in optimization. Consider this:
my point was that the attitude that every optimization allowed is required is not
helpful and is in the end counter productive.
actually, to be a bit cute about it, i should announce the first
international obfuscated c compiler contest. the goal of the contest
is to write a c99-compliant compiler that breaks every program in /sys/src/cmd.
the winner will be chosen based on highest percentage of programs broken,
with the tie going to the most devious tricks for remaining standards compliant
while missing the spirit completely.
> > 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.
- erik
next prev parent reply other threads:[~2012-10-29 23:10 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 [this message]
2012-10-29 23:26 ` Bakul Shah
2012-10-29 23:31 ` Bakul Shah
2012-10-29 23:36 ` erik quanstrom
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=0f05642b113b3ecfc160e82a9ca4db32@brasstown.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).