From: rixed@happyleptic.org
To: caml-list@inria.fr
Subject: Re: [Caml-list] ackermann microbenchmark strange results
Date: Wed, 24 Apr 2013 19:26:54 +0200 [thread overview]
Message-ID: <20130424172654.GA5722@shuttle.happyleptic.org> (raw)
In-Reply-To: <51780360.3020607@frisch.fr>
-[ Wed, Apr 24, 2013 at 06:08:00PM +0200, Alain Frisch ]----
> +1
>
> I've already seen 20% speedup obtained by adding some dead code (in
> an OCaml program, but this is irrelevant).
Remember me of a paper I read some years ago that was measuring the effect of
the various optimisation levels of gcc against the effect of addresses choices
(randomised using environment strings of various lengths!), and which
conclusion was that the effect of -O3 compared to -O2 was less than the effect
of "choosing" a good environment string :-)
Couldn't find it again using Google ; maybe someone remember this paper?
next prev parent reply other threads:[~2013-04-24 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 10:35 ygrek
2013-04-24 15:57 ` John Carr
2013-04-24 16:08 ` Alain Frisch
2013-04-24 16:57 ` Anthony Tavener
2013-04-24 17:26 ` rixed [this message]
2013-04-24 17:31 ` Török Edwin
2013-04-24 17:35 ` Matteo Frigo
2013-04-26 3:31 ` ygrek
2013-04-24 17:40 ` Xavier Leroy
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=20130424172654.GA5722@shuttle.happyleptic.org \
--to=rixed@happyleptic.org \
--cc=caml-list@inria.fr \
/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).