Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rewrite_stack_ptr post process pass #3046

Closed
ESI-SYD opened this issue Dec 19, 2024 · 1 comment · Fixed by #3497
Closed

rewrite_stack_ptr post process pass #3046

ESI-SYD opened this issue Dec 19, 2024 · 1 comment · Fixed by #3497
Assignees

Comments

@ESI-SYD
Copy link
Contributor

ESI-SYD commented Dec 19, 2024

Describe the bug

Changes from that PR #3010 introduced some duplicate code, should revisit and clean, then upstream.

Environment details

PVC

@ESI-SYD
Copy link
Contributor Author

ESI-SYD commented Feb 18, 2025

According to upstream reviewer's latest suggestion from triton-lang/triton#5878, we change to try add a intel post process pass instead of current targetInfo solution #3224 .

Status: Code drafted locally branch

@ESI-SYD ESI-SYD changed the title Code changes clean after #3010 rewrite_stack_ptr post process pass Feb 24, 2025
@ESI-SYD ESI-SYD linked a pull request Feb 24, 2025 that will close this issue
ESI-SYD added a commit that referenced this issue Mar 7, 2025
This PR have following changes:

1. Discard adding `TargetInfo::getStackPointer` that only exist in this
fork(then we keep the same as upstream), replace it with an intel pass
per discussion in
#3046 (comment).

2. Use public `ControlFlowOpToLLVM` and sync public `funcOpToLLVM` to
`PipelineManger` (difficult to use the public `FuncOpToLLVM` directly as
it contains Nv-specific codes) to match calling convention.

3. Lit tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment