From: Joel Reymont <joelr1@gmail.com>
To: "Markus Mottl" <markus.mottl@gmail.com>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Inlining and code placement
Date: Thu, 3 May 2007 21:37:31 +0100 [thread overview]
Message-ID: <5885F0FA-0125-4B35-BB94-8D15CCDBC502@gmail.com> (raw)
In-Reply-To: <f8560b80705031331y76bbcf12r9d48f4c21449d5b7@mail.gmail.com>
Markus,
Do you care to elaborate?
Thanks, Joel
On May 3, 2007, at 9:31 PM, Markus Mottl wrote:
> On 5/3/07, mmottl@janestcapital.com <mmottl@janestcapital.com> wrote:
>> concerning my email about inlining from a few days ago: it seems that
>> the majority of differences is not so much due to the inlining
>> level but
>> due to code placement. This means that playing with the inlining
>> level
>> beyond some reasonable, small value is likely to not have any strong
>> impact on the performance of the program.
--
http://wagerlabs.com/
prev parent reply other threads:[~2007-05-03 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 20:29 mmottl
2007-05-03 20:31 ` [Caml-list] " Markus Mottl
2007-05-03 20:37 ` Joel Reymont [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=5885F0FA-0125-4B35-BB94-8D15CCDBC502@gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@inria.fr \
--cc=markus.mottl@gmail.com \
/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).