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.

Sign up for GitHub

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

Constant evaluation should not impose TVM datatypes restrictions for intermediate values #914

Open
anton-trunov opened this issue Oct 5, 2024 · 0 comments
Open

Constant evaluation should not impose TVM datatypes restrictions for intermediate values #914

anton-trunov opened this issue Oct 5, 2024 · 0 comments
Assignees
@jeshecdom
Labels
scope: const-eval The constant and partial evaluation optimization mechanisms
Milestone
v1.6.0

Comments

@anton-trunov
Copy link
Member

The restrictions should only apply to the final result. This would allow things like -pow2(256) to mean TVM minimal integer instead of using integer literals (and hardcoding the unary minus rule for those).
@anton-trunov anton-trunov added the scope: const-eval The constant and partial evaluation optimization mechanisms label Oct 5, 2024
@anton-trunov anton-trunov added this to the v1.6.0 milestone Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeshecdom jeshecdom

Labels
scope: const-eval The constant and partial evaluation optimization mechanisms
Projects
None yet
Milestone
v1.6.0
Development

No branches or pull requests
2 participants
@jeshecdom @anton-trunov