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

Handle Parsing of Type Tree's passed as metadata #65

Closed
wsmoses opened this issue Oct 4, 2020 · 3 comments
Closed

Handle Parsing of Type Tree's passed as metadata #65

wsmoses opened this issue Oct 4, 2020 · 3 comments
Assignees

Comments

@wsmoses
Copy link
Member

wsmoses commented Oct 4, 2020

No description provided.

@wsmoses wsmoses self-assigned this Oct 4, 2020
@vchuravy
Copy link
Member

vchuravy commented Oct 4, 2020

Yeah in particular we want to remove the special cases for Julia in the tbaa analysis.

@wsmoses
Copy link
Member Author

wsmoses commented Oct 4, 2020

I think there's two separate things here that need to be done

  1. An interface for passing in TypeTree's at the calling boundary
  2. An extension mechanism to Type Analysis to handle custom rules (e.g. jl_apply_generic)

@wsmoses
Copy link
Member Author

wsmoses commented Dec 14, 2020

Incidentally this is now (partially) handled by #93 .

We still need the special case for Julia TBAA info presently (unless we ahead-of-time add calls to enzyme_float, etc) as the custom rule is only for functions, not for custom TBAA info.

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

No branches or pull requests

2 participants