From: "Andrew Kennedy" <akenn@microsoft.com>
To: "Brian Hurt" <brian.hurt@qlogic.com>,
"Ocaml Mailing List" <caml-list@inria.fr>
Subject: RE: [Caml-list] @, List.append, and tail recursion
Date: Fri, 24 Jan 2003 15:35:05 -0000 [thread overview]
Message-ID: <92FC642DD24AC94AA356906BD9FCD2D8D8422F@tvp-msg-03.europe.corp.microsoft.com> (raw)
Brian,
The optimization you describe is sometimes known as
"tail modulo cons", and is an example of "destination-passing
style". In other words, the place to put the result (in
this case, the address of the tail of a just-constructed
cons cell) is passed on in a tail-recursive call.
See "A Functional Representation of Data Structures with a Hole"
by Minamide in POPL'98.
http://www.score.is.tsukuba.ac.jp/~minamide/index.html
Although Minimide formalizes the problem in the context of
a typed intermediate language, it's probably quite easy to
spot special cases quite far down the compiler pipeline.
- Andrew.
> -----Original Message-----
> From: Brian Hurt [mailto:brian.hurt@qlogic.com]
> Sent: Friday, January 24, 2003 12:48 AM
> To: Ocaml Mailing List
> Subject: [Caml-list] @, List.append, and tail recursion
>
>
>
> I hit a bug recently wiith @ and List.append. Since they're
> recursive,
> not tail-recursive, on long enough lists Ocaml thinks you've gone
> infinitely recursive and aborts. The code:
>
>
> let longlist len =
> let rec longlist_int v c acc =
> if (c == 0) then acc else longlist_int (v + 1) (c -
> 1) (v :: acc)
> in
> longlist_int 0 len []
> ;;
>
> let x = longlist 65536 ;;
>
> List.append x [] ;;
>
> Exits with:
>
> Stack overflow during evaluation (looping recursion?).
>
> So does:
> x @ [] ;;
>
> You can work around this like:
>
> let append' a b =
> List.rev_append (List.rev a) b
> ;;
>
> Since both rev_append and rev are tail recursive (looping) and not
> recursive, this works. But some ad-hoc testing says that
> this method is
> about 50% slower than normal append for lists short enough
> not to abort.
>
> Thinking about this, I realized that my code is doing stuff
> like this all over the place. I'm basically doing sparse
> vector/matrix stuff, handling
> (effectively) (colno * value) list for vectors, and (rowno *
> vector) list for matrix. And I may be hitting lists long
> enough to trip the problem.
>
> Which means I'm currently doing a lot of recursion of the form:
>
> let rec foo x =
> match x with
> [] -> []
> | head :: tail -> (expr head) :: (foo tail)
> ;;
>
> for various complexities. And it has occured to me that all of these
> forms *should* be optimizable into loops. The general case
> would work
> something like this in C:
>
> struct list_t {
> void * datum;
> struct list_t * next_p;
> }
>
> struct list_t * foo (struct list_t * x) {
> struct list_t * retval = NULL;
> struct list_t ** ptr_pp = &retval;
>
> while (x != NULL) {
> struct list_t * temp = alloc(sizeof(struct list_t));
> *ptr_pp = temp;
> temp->datum = expr(x->datum);
> temp->next_p = NULL; /* be nice to the GC */
> ptr_pp = &(temp->next_p);
> x = x->next_p;
> }
> return retval;
> }
>
> If expr() returned a list, the only change necessary would be
> to find the
> end of the list before moving on, like:
>
> struct list_t * foo (struct list_t * x) {
> struct list_t * retval = NULL;
> struct list_t ** ptr_pp = &retval;
>
> while (x != NULL) {
> *ptr_p = expr(x->datum); /* expr allocates the list */
> /* We assume the last element of the list expr() returned has
> * NULL for next_p.
> */
> while (*ptr_p != NULL) {
> ptr_p = &((*ptr_p)->next_p);
> }
> x = x->next_p;
> }
> return retval;
> }
>
> Rather than just looking at making @ an inline C function, I
> think we (the
> Ocaml community) should be looking at adding this more general
> optimization in.
>
> So now we get to my two questions:
> a) is anyone working on this/intending to work on this RSN?
> b) if the answer to (a) is no, can anyone give me some
> pointers on where
> to start looking at code, so I can add it in?
>
> Brian
>
>
> -------------------
> 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 reply other threads:[~2003-01-24 15:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 15:35 Andrew Kennedy [this message]
2003-01-30 1:44 ` brogoff
2003-01-30 9:57 ` Christophe Raffalli
2003-01-30 16:03 ` Brian Hurt
2003-01-31 10:33 ` Mattias Waldau
-- strict thread matches above, loose matches on Subject: below --
2003-01-31 22:27 Harrison, John R
2003-01-31 19:58 Harrison, John R
2003-01-31 21:04 ` Brian Hurt
2003-01-31 17:32 Diego Olivier Fernandez Pons
2003-01-24 0:48 Brian Hurt
2003-01-30 18:10 ` Olivier Andrieu
2003-01-30 19:46 ` Brian Hurt
2003-01-30 20:52 ` Olivier Andrieu
2003-01-30 21:57 ` Brian Hurt
2003-01-31 2:16 ` james woodyatt
2003-01-31 17:05 ` Diego Olivier Fernandez Pons
2003-01-31 19:52 ` Brian Hurt
2003-01-31 21:34 ` Issac Trotts
2003-01-31 17:13 ` Brian Hurt
2003-01-31 17:42 ` brogoff
2003-01-31 19:18 ` Russ Ross
2003-01-31 19:32 ` Alexander V. Voinov
2003-02-01 2:30 ` brogoff
2003-01-31 23:12 ` Issac Trotts
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=92FC642DD24AC94AA356906BD9FCD2D8D8422F@tvp-msg-03.europe.corp.microsoft.com \
--to=akenn@microsoft.com \
--cc=brian.hurt@qlogic.com \
--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