From: Walid Taha <taha@cs.rice.edu>
To: Andrew Lenharth <andrewl@debian.org>
Cc: William Chesters <williamc@paneris.org>, <caml-list@inria.fr>
Subject: Re: [Caml-list] partial eval question
Date: Tue, 3 Feb 2004 20:59:57 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.44.0402032057210.17089-100000@boromir.cs.rice.edu> (raw)
In-Reply-To: <20031027185021.GA1793@vilya.homelinux.net>
On Mon, 27 Oct 2003, Andrew Lenharth wrote:
|On Mon, Oct 27, 2003 at 03:39:21PM +0000, William Chesters wrote:
|> And that's an improvement over
|>
|> double pow(double x, int n) {
|> double it = 1;
|> while (--n >= 0) it *= x;
|> return it;
|> }
|>
|> double pow3(double x, int n) {
|> return pow(x, 3);
|> }
|>
|> in what way exactly? (If it doesn't work for you, try
|> -funroll-all-loops.)
|
|And that's an improvement over
|
|template <int N>
|inline double pow (double x) {
| return x * pow<N-1>(x);
|}
|template<>
|inline double pow<0> (double x) {
| return 1.0;
|}
|
|in what way exactly? (If it doesn't work for you, try
|-O2) :)
OK. There is an article specifically about this point:
http://www.cs.rice.edu/~taha/publications/preprints/2003-12-01.pdf
(Comments are welcome, actually, the paper is undergoing the final
revision).
|The C example relies on a fairly smart compiler to
|do interprocedual analysis. The C++ example
|only requires the inline keywork be honored, and you
|don't need explicit pow3 pow2, you have pow<3> pow<2>
|pow<any constant>.
|
|Gives a bit more control over code generation.
The draw back with C++ templates, in this case, is that you have to wait
until the C++ code is generate before you know it type checks. A key goal
of MSP is to ensure that generated code is *always* well-typed. That
actually has been achieved in the context of a wide-range of type systems.
Walid.
|Andrew
|
|-------------------
|To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
|Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
|Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
|
--
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-02-04 3:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 1:41 Ben Kavanagh
2003-10-27 7:14 ` Damien
2003-10-27 15:39 ` William Chesters
2003-10-27 18:50 ` Andrew Lenharth
2003-10-27 19:12 ` William Chesters
2003-10-27 20:08 ` Jacques Carette
2004-02-04 3:03 ` Walid Taha
2003-10-27 22:11 ` Andrew Lenharth
2004-02-04 2:59 ` Walid Taha [this message]
2004-02-04 5:53 ` Andrew Lenharth
2004-02-05 21:29 ` Walid Taha
2003-10-27 19:17 ` Yann Regis-Gianas
2003-10-28 10:46 ` William Chesters
2004-02-04 2:22 ` Walid Taha
2004-02-04 2:56 ` Walid Taha
2003-10-28 15:09 ` Dmitry Lomov
2003-10-27 15:16 ` Vincent Balat [prof Moggi team]
2004-02-04 2:51 ` Walid Taha
2004-02-04 10:26 ` Ben Kavanagh
2004-02-04 10:32 ` Ben Kavanagh
2004-02-05 21:11 ` Walid Taha
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=Pine.LNX.4.44.0402032057210.17089-100000@boromir.cs.rice.edu \
--to=taha@cs.rice.edu \
--cc=andrewl@debian.org \
--cc=caml-list@inria.fr \
--cc=williamc@paneris.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