Skip to content

Conversation

@krishnamtibrewala
Copy link
Collaborator

No description provided.

@martien-de-jong
Copy link
Collaborator

It would be nice to have a description of the tail call strategy. It's intricate management of the stack, We need to setup arguments to the tail callee, we need to restore the callee saved registers, I would like to know what determines whether something is a tail call, do we try to free up as much stack as possible, etc.

@krishnamtibrewala krishnamtibrewala force-pushed the aie-tail-call branch 3 times, most recently from c0cb1e2 to 199ba27 Compare April 7, 2025 18:49
@krishnamtibrewala krishnamtibrewala changed the title [WIP][AIEX] Support simple TCO [AIEX] Support simple Tail Call Opt Apr 7, 2025
@krishnamtibrewala krishnamtibrewala marked this pull request as ready for review April 7, 2025 18:51
Copy link
Collaborator

@konstantinschwarz konstantinschwarz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thanks for applying all comments.
I think this looks good as an initial version of tail call optimization.
Handling more complicated scenarios can come as follow-up work.

@krishnamtibrewala krishnamtibrewala merged commit 4e36470 into aie-public Apr 8, 2025
6 checks passed
@konstantinschwarz konstantinschwarz deleted the aie-tail-call branch April 8, 2025 22:22
mgehre-amd pushed a commit that referenced this pull request Aug 21, 2025
[AutoBump] Merge with 8280651 (Sep 17) (5)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants