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

Fix division range estimation error in simplifier #6244

Merged
merged 1 commit into from
Aug 11, 2020
Merged

Fix division range estimation error in simplifier #6244

merged 1 commit into from
Aug 11, 2020

Conversation

kparzysz-quic
Copy link
Contributor

Division a/b assumes maximum values when b is close to 0. Account for that when estimating the range for a/b when 0 belongs to the estimated range for b.

Assume that a division by zero cannot happen in a valid program, so in such cases treat the range for b as a union [b.min_value, -1] u [1, b.max_value].

Division a/b assumes maximum values when b is close to 0. Account
for that when estimating the range for a/b when 0 belongs to the
estimated range for b.

Assume that a division by zero cannot happen in a valid program,
so in such cases treat the range for b as a union
  [b.min_value, -1] u [1, b.max_value]
@tqchen tqchen merged commit 12da324 into apache:master Aug 11, 2020
@tqchen
Copy link
Member

tqchen commented Aug 11, 2020

Thanks @kparzysz-quic !

@kparzysz-quic kparzysz-quic deleted the div-bounds branch August 11, 2020 15:56
wjliu1998 pushed a commit to wjliu1998/incubator-tvm that referenced this pull request Aug 13, 2020
Division a/b assumes maximum values when b is close to 0. Account
for that when estimating the range for a/b when 0 belongs to the
estimated range for b.

Assume that a division by zero cannot happen in a valid program,
so in such cases treat the range for b as a union
  [b.min_value, -1] u [1, b.max_value]
trevor-m pushed a commit to trevor-m/tvm that referenced this pull request Aug 26, 2020
Division a/b assumes maximum values when b is close to 0. Account
for that when estimating the range for a/b when 0 belongs to the
estimated range for b.

Assume that a division by zero cannot happen in a valid program,
so in such cases treat the range for b as a union
  [b.min_value, -1] u [1, b.max_value]
trevor-m pushed a commit to trevor-m/tvm that referenced this pull request Aug 26, 2020
Division a/b assumes maximum values when b is close to 0. Account
for that when estimating the range for a/b when 0 belongs to the
estimated range for b.

Assume that a division by zero cannot happen in a valid program,
so in such cases treat the range for b as a union
  [b.min_value, -1] u [1, b.max_value]
trevor-m pushed a commit to trevor-m/tvm that referenced this pull request Aug 26, 2020
Division a/b assumes maximum values when b is close to 0. Account
for that when estimating the range for a/b when 0 belongs to the
estimated range for b.

Assume that a division by zero cannot happen in a valid program,
so in such cases treat the range for b as a union
  [b.min_value, -1] u [1, b.max_value]
trevor-m pushed a commit to trevor-m/tvm that referenced this pull request Sep 2, 2020
Division a/b assumes maximum values when b is close to 0. Account
for that when estimating the range for a/b when 0 belongs to the
estimated range for b.

Assume that a division by zero cannot happen in a valid program,
so in such cases treat the range for b as a union
  [b.min_value, -1] u [1, b.max_value]
trevor-m pushed a commit to neo-ai/tvm that referenced this pull request Sep 3, 2020
Division a/b assumes maximum values when b is close to 0. Account
for that when estimating the range for a/b when 0 belongs to the
estimated range for b.

Assume that a division by zero cannot happen in a valid program,
so in such cases treat the range for b as a union
  [b.min_value, -1] u [1, b.max_value]
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.

2 participants