From: Chris Hecker <checker@d6.com>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] two unrelated questions
Date: Thu, 26 Apr 2001 15:34:31 -0700 [thread overview]
Message-ID: <4.3.2.7.2.20010426153132.026a2220@shell16.ba.best.com> (raw)
In-Reply-To: <20010426154727.E29782@pauillac.inria.fr>
>It's an embarrassing example of two distinct optimizations that
>conflict, resulting in bad code :-)
Ah, thanks. I have a strange talent for breaking things, I've found over the years. The first thing I try never works. I'd make a good tester. :)
> The bytecode compiler performs no inlining at all.
Why is this? I can think of a few reasonable arguments:
- if you want speed you'll compile to native
- bytecode is for size, and inlining hoses this
- you tested it on real-size apps and found cache coherency made non-inlines faster
- it's hard for some reason I don't understand
- haven't gotten around to it yet
- ???
Chris
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-04-26 22:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 21:08 Chris Hecker
2001-04-26 0:38 ` Patrick M Doane
2001-04-26 6:04 ` Judicaël Courant
2001-04-26 12:06 ` John Max Skaller
2001-04-27 9:12 ` Anton Moscal
2001-04-29 22:24 ` Brian Rogoff
2001-04-30 18:57 ` Fergus Henderson
2001-05-01 1:31 ` Jacques Garrigue
2001-05-01 12:45 ` [Caml-list] " Ken Friis Larsen
2001-04-27 15:09 ` [Caml-list] " Brian Rogoff
2001-04-27 17:49 ` John Max Skaller
2001-04-26 8:22 ` Andreas Rossberg
2001-04-26 1:13 ` Jacques Garrigue
2001-04-26 13:47 ` Xavier Leroy
2001-04-26 22:34 ` Chris Hecker [this message]
2001-04-26 16:57 ` Mark Seaborn
2001-04-26 22:20 ` John Max Skaller
2001-05-01 21:08 ` Brian Rogoff
2001-05-01 23:30 ` John Max Skaller
2001-05-02 0:03 ` John Max Skaller
2001-05-01 17:25 Dave Berry
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=4.3.2.7.2.20010426153132.026a2220@shell16.ba.best.com \
--to=checker@d6.com \
--cc=Xavier.Leroy@inria.fr \
--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).