From: Jon Harrop <jonathandeanharrop@googlemail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocamlopt performance in 3.11
Date: Fri, 31 Oct 2008 23:58:03 +0000 [thread overview]
Message-ID: <200810312358.03757.jon@ffconsultancy.com> (raw)
In-Reply-To: <48FC3E20.2090206@gmail.com>
On Monday 20 October 2008 09:15:28 Alain wrote:
> David Allsopp wrote:
> > OK, so I've tried using the -nodynlink option with all calls to ocamlopt
> > and spotted *no* timing difference. A quick binary comparison of the EXE
> > produced reveals that ocamlopt -nodynlink is making ABSOLUTELY NO
> > difference in the resulting code.
>
> -nodynlink only makes a difference for the AMD64 backend. It is accepted
> by ocamlopt for all ports in order to simplify Makefiles.
Would be good if all command line options to the compilers (e.g. -ffast-math)
were accepted by ocamlopt on all ports for the same reason.
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
prev parent reply other threads:[~2008-10-31 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 9:59 David Allsopp
2008-10-17 12:32 ` [Caml-list] " Andres Varon
2008-10-18 16:36 ` David Allsopp
2008-10-20 8:15 ` Alain
2008-10-20 12:11 ` David Allsopp
2008-10-31 23:58 ` Jon Harrop [this message]
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=200810312358.03757.jon@ffconsultancy.com \
--to=jonathandeanharrop@googlemail.com \
--cc=caml-list@yquem.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