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

[mlir] support unknown (top) state in aliasing and activity analysis #1569

Merged
merged 5 commits into from
Jan 2, 2024

Conversation

ftynse
Copy link
Collaborator

@ftynse ftynse commented Dec 7, 2023

Also add conservative handling of unknown situations in alias analysis.

Copy link
Member

@pengmai pengmai left a comment

Choose a reason for hiding this comment

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

Looks great! I just have some small things, nothing that should block this PR.

enzyme/Enzyme/MLIR/Analysis/DataFlowActivityAnalysis.cpp Outdated Show resolved Hide resolved
enzyme/Enzyme/MLIR/Analysis/AliasAnalysis.cpp Outdated Show resolved Hide resolved
enzyme/Enzyme/MLIR/Analysis/DataFlowActivityAnalysis.cpp Outdated Show resolved Hide resolved
- Update the points-to lattice to indicate that "other" pointers may
  have pointers to unknown location stored, but some specific pointers
  may have pointers to known locations.
- Add a trivial may/must write differentiation.
- The tests are *NOT* fully updated.
* some support is still missing in printers of activity analyses
* three tests are failing because they produce different results now
  (haven't investigated if the previous expectations were correct)
* Fix points-to-pointer analysis to return "other" value, which may be
  empty set (lattice bottom) rather than always returning "any"
  (lattice top).
* Don't get tricked by operator[] on maps default-initializing the value
  in `map[key] == deafult_value` comparison attempting to see if the map
  changed.
* Propagate changes in two places.
* Fix "other" in/out activity state in dense (pointer) activity
  analysis.
@ftynse ftynse enabled auto-merge January 2, 2024 11:53
@wsmoses wsmoses disabled auto-merge January 2, 2024 15:42
@wsmoses wsmoses merged commit a6e8dc0 into main Jan 2, 2024
42 of 58 checks passed
@wsmoses wsmoses deleted the ftynse/unfixed branch January 2, 2024 15:42
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.

3 participants