We have discussed (in tail recursion) that a recursive function is tail recursive if recursive call is the last thing executed by the function.
We also discussed that a tail recursive is better than non-tail recursive as tail-recursion can be optimized by modern compilers. Modern compiler basically do tail call elimination to optimize the tail recursive code.
If we take a closer look at above function, we can remove the last call with goto. Below are examples of tail call elimination.
The above function can be replaced by following after tail call elimination.
Therefore job for compilers is to identify tail recursion, add a label at the beginning and update parameter(s) at the end followed by adding last goto statement.
This article is contributed by Dheeraj Jain. Please write comments if you find anything incorrect, or you want to share more information about the topic discussed above
- QuickSort Tail Call Optimization (Reducing worst case space to Log n )
- Tail Recursion
- Tail Recursion for Fibonacci
- Tail recursion to calculate sum of array elements.
- Queries to find the count of characters preceding the given location
- Find the path from root to the given nodes of a tree for multiple queries
- Count number of steps to cover a distance if steps can be taken in powers of 2
- Minimum increment or decrement operations required to make the array sorted
- Queries to find the left-most given type integer in a binary array
- Blowfish Algorithm with Examples
- Longest Increasing Subsequence using Longest Common Subsequence Algorithm
- Minimum number of additons to make the string balanced
- Find a pair (n,r) in an integer array such that value of nPr is maximum
- Find a pair (n,r) in an integer array such that value of nCr is maximum