-
Notifications
You must be signed in to change notification settings - Fork 273
bv_cbmct::unbounded_arrayt::U_AUTO is never enabled #2018
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
Labels
Comments
tautschnig
added a commit
to tautschnig/cbmc
that referenced
this issue
Apr 25, 2018
Previously, the command line permitted setting uninterpreted functions to "never" or "always", where "never" actually was the default. The "automatic" mode could not be enabled in any way. Furthermore the limit should apply across all dimensions of an array, not just the top-level size. Fixes: diffblue#2018
tautschnig
added a commit
to tautschnig/cbmc
that referenced
this issue
Apr 13, 2019
Previously, the command line permitted setting uninterpreted functions to "never" or "always", where "never" actually was the default. The "automatic" mode could not be enabled in any way. Furthermore the limit should apply across all dimensions of an array, not just the top-level size. Fixes: diffblue#2018
tautschnig
added a commit
to tautschnig/cbmc
that referenced
this issue
May 29, 2019
Previously, the command line permitted setting uninterpreted functions to "never" or "always", where "never" actually was the default. The "automatic" mode could not be enabled in any way. Furthermore the limit should apply across all dimensions of an array, not just the top-level size. Fixes: diffblue#2018
tautschnig
added a commit
to tautschnig/cbmc
that referenced
this issue
May 30, 2019
Previously, the command line permitted setting uninterpreted functions to "never" or "always", where "never" actually was the default. The "automatic" mode could not be enabled in any way. Furthermore the limit should apply across all dimensions of an array, not just the top-level size. Fixes: diffblue#2018
tautschnig
added a commit
to tautschnig/cbmc
that referenced
this issue
Jun 1, 2019
Previously, the command line permitted setting uninterpreted functions to "never" or "always", where "never" actually was the default. The "automatic" mode could not be enabled in any way. Furthermore the limit should apply across all dimensions of an array, not just the top-level size. Fixes: diffblue#2018
tautschnig
added a commit
to tautschnig/cbmc
that referenced
this issue
May 20, 2021
Previously, the command line permitted setting uninterpreted functions to "never" or "always", where "never" actually was the default. The "automatic" mode could not be enabled in any way. Furthermore the limit should apply across all dimensions of an array, not just the top-level size. Fixes: diffblue#2018
tautschnig
added a commit
to tautschnig/cbmc
that referenced
this issue
Dec 8, 2022
Previously, the command line permitted setting uninterpreted functions to "never" or "always", where "never" actually was the default. The "automatic" mode could not be enabled in any way. This reverts diffblue#6232, but now includes additional changes to the array theory to handle nested struct members no different from members of a top-level struct. Fixes: diffblue#2018
tautschnig
added a commit
to tautschnig/cbmc
that referenced
this issue
Dec 8, 2022
Previously, the command line permitted setting uninterpreted functions to "never" or "always", where "never" actually was the default. The "automatic" mode could not be enabled in any way. This reverts diffblue#6232, but now includes additional changes to the array theory to handle nested struct members no different from members of a top-level struct. Fixes: diffblue#2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While seemingly meant to be the default (only never/always can be set via the command line), the default is actually
U_NONE
. Enabling it is trivial, but will break lots of examples until #1086 is complete and merged. Furthermore it seems current code only looks at the top-level size, not the nested values. Below is a patch that may be a useful starting point:The text was updated successfully, but these errors were encountered: