From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] tool (that wnj wrote?) that reduced the data segment size?
Date: Sun, 29 Nov 2015 22:07:02 -0500 [thread overview]
Message-ID: <20151130030702.GF32175@mercury.ccil.org> (raw)
In-Reply-To: <CANV78LS-wQEswOg7GMFcv4vwqtEJj=-z38isNtzJDW1ukhKd=w@mail.gmail.com>
Charles Anthony scripsit:
> "The Optimizing Compiler Writer's Motto: It is no sin to make a wrong
> program worse."
It is if the rules for which programs are wrong are essentially beyond
human comprehension on the fly. Anyway: "That program has about a
thousand bugs. Which would you rather, that we fixed all the bugs or
that we made it run a thousand times faster?"
--
John Cowan http://www.ccil.org/~cowan cowan at ccil.org
Heckler: "Go on, Al, tell 'em all you know. It won't take long."
Al Smith: "I'll tell 'em all we *both* know. It won't take any longer."
next prev parent reply other threads:[~2015-11-30 3:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 23:30 Norman Wilson
2015-11-28 23:38 ` Charles Anthony
2015-11-30 3:07 ` John Cowan [this message]
2015-11-30 5:38 ` Nick Downing
-- strict thread matches above, loose matches on Subject: below --
2015-11-28 14:58 Doug McIlroy
2015-11-27 22:26 Larry McVoy
2015-11-27 23:44 ` Dave Horsfall
2015-11-28 0:03 ` Larry McVoy
2015-11-30 2:45 ` Erik E. Fair
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=20151130030702.GF32175@mercury.ccil.org \
--to=cowan@mercury.ccil.org \
/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).