Re: Tail-Call Elimination Use-Cases

> gcc 3 has new tail call and sibling call optimizations, and they are working
> fairly well. Further improvements are possible, but that is a matter of
> finding volunteers interested in working on this part of GCC.


It is *very* limited and therefore gets hardly used. A few limitations
are:


  - signature of caller and callee must match; there is no tail-call, but
      tail-recursion implemented


  - stack frames must be empty (or not grow larger than byte-alignment
      restrictions allow), i.e. tail-recursion fails if there are local
      arrays initialised and the like


  - no indirect calls possible


  - ...


There's a few more, but that's just to show how limited this feature in
gcc currently is. And yes, I'm a volunteer for this matter, as you
might call it.


--
(o_ Andreas Bauer, baueran at in.tum.de, http://home.in.tum.de/baueran/

Return to the comp.compilers page.
Search the comp.compilers archives again.