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

Triggers not ideally chosen for generated predicate axioms #291

Open
viper-admin opened this issue Nov 20, 2019 · 1 comment
Open

Triggers not ideally chosen for generated predicate axioms #291

viper-admin opened this issue Nov 20, 2019 · 1 comment
Labels
bug Something isn't working major performance

Comments

@viper-admin
Copy link
Member

Created by @gauravpartha on 2019-11-20 16:59
Last updated on 2019-11-29 12:35

The translation of the Viperpredicate P(x: Ref) leads to the following two axioms that are generated on the Boogie side:

axiom (forall x: Ref, x2: Ref ::
  { P(x), P(x2) }
  P(x) == P(x2) ==> x == x2
);

axiom (forall x: Ref, x2: Ref ::
  { P#sm(x), P#sm(x2) }
  P#sm(x) == P#sm(x2) ==> x == x2
);

This is not ideal, because the corresponding triggers lead to a quadratic number of instantiations. It would be nice to get rid of this with an inverse function construction (similarly to how one usually encodes injectivity).

@viper-admin
Copy link
Member Author

@fabiopakk on 2019-11-29 12:35:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working major performance
Projects
None yet
Development

No branches or pull requests

3 participants