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

Find another location where get_ikind results in an error #41

Merged
merged 2 commits into from
Jul 19, 2022

Conversation

Dudeldu
Copy link
Owner

@Dudeldu Dudeldu commented Jul 15, 2022

I rare cases (sv-comp: floats-cbmc-regression/float21.yml) the check on is_safe_cast throws an exception due to a call to get_ikind on potentially float arguments inside IntDomain.Size.is_cast_injective. Now we directly ignore all casts that have a float-like part.

@Dudeldu Dudeldu requested a review from FelixKrayer July 15, 2022 14:10
FelixKrayer
FelixKrayer previously approved these changes Jul 18, 2022
@FelixKrayer
Copy link
Collaborator

Do you want to add the svcomp test? I personally do not think it's really necessary here

@Dudeldu Dudeldu force-pushed the fix-ikind-issue-in-cast-check branch from 4f241da to ff56a9e Compare July 18, 2022 13:57
@FelixKrayer
Copy link
Collaborator

I trust, you know what you are doing with the safeness of casts from Float to Int, but seems reasonable

@Dudeldu Dudeldu merged commit d31be72 into master Jul 19, 2022
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