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

[Relax] Handle presence of R.call_tir in MergeCompositeFunctions #17220

Conversation

Lunderberg
Copy link
Contributor

Prior to this commit, use of R.call_tir in the input to MergeCompositeFunctions would result in a segfault, when attempting to determine the Group* that contains the relax::GlobalVar of the callee.

This commit updates MergeCompositeFunctions to check for relax::GlobalVar and relax::Tuple instances.

Closes #17120

Prior to this commit, use of `R.call_tir` in the input to
`MergeCompositeFunctions` would result in a segfault, when attempting
to determine the `Group*` that contains the `relax::GlobalVar` of the
callee.

This commit updates `MergeCompositeFunctions` to check for
`relax::GlobalVar` and `relax::Tuple` instances.

Closes apache#17120
@tqchen tqchen merged commit 8680c39 into apache:main Jul 31, 2024
18 checks passed
@Lunderberg Lunderberg deleted the bugfix_check_for_global_var_in_merge_composite_functions branch July 31, 2024 19:35
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.

[Relax][Bug] Segmentation fault when using the MergeCompositeFunctions transform
2 participants