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

PR for llvm/llvm-project#64289 #556

Merged
merged 2 commits into from
Aug 9, 2023
Merged

PR for llvm/llvm-project#64289 #556

merged 2 commits into from
Aug 9, 2023

Conversation

llvmbot
Copy link
Member

@llvmbot llvmbot commented Aug 9, 2023

DianQK added 2 commits August 9, 2023 04:22
For checking the readonly attribute.

Pre-commit test for D156793.

Reviewed By: nikic

Differential Revision: https://reviews.llvm.org/D156789

(cherry picked from commit b77e556)
When eliminating a tail call, we modify the values of the arguments.
Therefore, if the byval parameter has a readonly attribute, we have to remove it. It is safe because,
from the perspective of a caller, the byval parameter is always treated as "readonly," even if the readonly attribute is removed.

Fixes #64289.

Reviewed By: nikic

Differential Revision: https://reviews.llvm.org/D156793

(cherry picked from commit c3f227e)
@llvmbot
Copy link
Member Author

llvmbot commented Aug 9, 2023

@nikic @nikic What do you think about merging this PR to the release branch?

@nikic
Copy link
Contributor

nikic commented Aug 9, 2023

LGTM

@tru tru merged commit 3a2aea9 into release/17.x Aug 9, 2023
@tru tru deleted the llvm-issue64289 branch August 9, 2023 06:58
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.

tailcallelim introduces write to readonly byval parameter
4 participants