* Tail Call Optimization
@ 2003-09-01 13:14 Singh Pradyuman-R50282
2003-09-01 14:24 ` Wojtek Narczynski
0 siblings, 1 reply; 2+ messages in thread
From: Singh Pradyuman-R50282 @ 2003-09-01 13:14 UTC (permalink / raw)
To: 'gcc-help@gcc.gnu.org'; +Cc: Singh Pradyuman-R50282
Hi,
Does anyone know of any definitive work on the tailcall optimization.
I'm looking for work on what can be risky situations in which tailcall can cause problems or some documents on what to watchout for while implementing tailcall.
Thanks in advance,
Pradyuman.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Tail Call Optimization
2003-09-01 13:14 Tail Call Optimization Singh Pradyuman-R50282
@ 2003-09-01 14:24 ` Wojtek Narczynski
0 siblings, 0 replies; 2+ messages in thread
From: Wojtek Narczynski @ 2003-09-01 14:24 UTC (permalink / raw)
To: Singh Pradyuman-R50282; +Cc: gcc-help
Hello,
> Does anyone know of any definitive work on the tailcall optimization.
> I'm looking for work on what can be risky situations in which tailcall
> can cause problems or some documents on what to watchout for while
> implementing tailcall.
It may be langage (being implemented) dependent. "Modern compiler
implementation in ML" by Andrew W. Appel covers this subject at basic
level.
I cannot think of any serious potential problems. The not serious ones
could be: 1. turing out-of-stack into infinite loop, 2. causing a very
badly written threaded program to go wild.
Regards,
Wojtek
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-09-01 14:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-01 13:14 Tail Call Optimization Singh Pradyuman-R50282
2003-09-01 14:24 ` Wojtek Narczynski
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 read-only IMAP folder(s) and NNTP newsgroup(s).