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

Replace IRTools with CodeInfoTools #117

Closed
yebai opened this issue Feb 9, 2022 · 3 comments · Fixed by #126
Closed

Replace IRTools with CodeInfoTools #117

yebai opened this issue Feb 9, 2022 · 3 comments · Fixed by #126
Assignees

Comments

@yebai
Copy link
Member

yebai commented Feb 9, 2022

No description provided.

@devmotion
Copy link
Member

Is it better? I am not familiar with the differences (according to the README it is based closely on IRTools) but it seems it is developed less actively and has fewer contributors (and is only used by Mixtape.jl but no other package yet).

@yebai
Copy link
Member Author

yebai commented Feb 9, 2022

CodeInfoTool is based on the new compiler data structures (i.e. CodeInfo) and APIs in Julia 1.7. Since CodeInfoTools is just a small set of utilities for making Julia's compiler API more friendly, it should be more stable than IRTools in general - that's probably why CodeInfoTools does not need any changes for a long time. In the worst case, it should not be hard to switch to using Julia's native compiler API from CodeInfoTools. However, Julia's compiler API is slightly less user-friendly in its current form.

@femtomc
Copy link

femtomc commented Feb 23, 2022

CodeInfoTool is based on the new compiler data structures (i.e. CodeInfo) and APIs in Julia 1.7. Since CodeInfoTools is just a small set of utilities for making Julia's compiler API more friendly, it should be more stable than IRTools in general - that's probably why CodeInfoTools does not need any changes for a long time. In the worst case, it should not be hard to switch to using Julia's native compiler API from CodeInfoTools. However, Julia's compiler API is slightly less user-friendly in its current form.

This is the right idea. CodeInfoTools should be thought of as an intermediate step before better APIs are actually part of Core.

All compiler caveats for stability still apply!

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 a pull request may close this issue.

4 participants