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

Jump to bottom

Readonly/readnone are derived after pointer escapes #40673

Closed
jdoerfert opened this issue Apr 1, 2019 · 1 comment
Closed

Readonly/readnone are derived after pointer escapes #40673

jdoerfert opened this issue Apr 1, 2019 · 1 comment
Labels
bugzilla Issues migrated from bugzilla ipo Interprocedural optimizations

Comments

@jdoerfert
Copy link
Member

Bugzilla Link 41328
Version trunk
OS Linux
Attachments problematic inputs
CC @hfinkel

Extended Description

Readnone/only pointer attribute detection ignores uses in calls if they are themselves marked as readnon/only. Though, even a readnone pointer use allows the pointer to escape. The test case shows how the wrong attributes are derived when optimized with -functionattrs.
@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 10, 2021
@nikic
Copy link
Contributor

nikic commented Feb 22, 2023

Has since been fixed.

@nikic nikic closed this as completed Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla ipo Interprocedural optimizations
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nikic @jdoerfert