Skip to content

Improve performance of cbmc's implementation of the gcc integer overflow primitives #5405

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
Open
danpoe opened this issue Jul 2, 2020 · 4 comments
Open

Improve performance of cbmc's implementation of the gcc integer overflow primitives #5405

danpoe opened this issue Jul 2, 2020 · 4 comments
Labels
aws Bugs or features of importance to AWS CBMC users Performance Optimisations

Comments

@danpoe
Copy link
Contributor

danpoe commented Jul 2, 2020 •
edited
Loading

See #4701 for potential ways of improving the performance.

Tracked internally as ADA-563.
@danpoe danpoe added Performance Optimisations aws Bugs or features of importance to AWS CBMC users labels Jul 2, 2020
@danpoe danpoe mentioned this issue Jul 2, 2020
Closed
@hannes-steffenhagen-diffblue
Copy link
Contributor

hannes-steffenhagen-diffblue commented Jul 9, 2020 •
edited
Loading

@danielsn Could you elaborate on your comment here? I.e. if you have some examples where these checks are causing problems, could you link to a couple here so we have something to benchmark against?

@hannes-steffenhagen-diffblue
Copy link
Contributor

This is internally tracked as ADA-563

@feliperodri
Copy link
Collaborator

@danielsn @hannes-steffenhagen-diffblue any updates on this issue? Should we close it?

@martin-cs martin-cs mentioned this issue Feb 21, 2021
Closed
@jimgrundy
Copy link
Collaborator

Dropped to low priority following discussion with @danielsn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
aws Bugs or features of importance to AWS CBMC users Performance Optimisations
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@feliperodri @danielsn @danpoe @hannes-steffenhagen-diffblue @jimgrundy