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

Disable SIMD intrinsics #1143

Merged
merged 2 commits into from
May 3, 2022
Merged

Conversation

adpaco-aws
Copy link
Contributor

@adpaco-aws adpaco-aws commented May 2, 2022

Description of changes:

Disables all SIMD intrinsics, which were not considered during the general intrinsics audit. The main concern is with these intrinsics is that overflow checks do not seem to be introduced for some of them.

Call-outs:

Testing:

  • How is this change tested? Converts 4 tests to "fixme".

  • Is this a refactor change? No.

Checklist

  • Each commit message has a non-empty body, explaining why the change was made
  • Methods or procedures are documented
  • Regression or unit tests are included, or existing tests cover the modified code
  • My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

@adpaco-aws adpaco-aws requested a review from a team as a code owner May 2, 2022 20:30
@nchong-at-aws
Copy link
Contributor

Looks reasonable to me, Adrian. Do we have a ticket to track re-enabling these intrinsics at some point?

fargs,
p,
cbmc_ret_ty,
n
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be _n

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had to add _ to all non-used variables, functions or macros because it would introduce a warning otherwise (the unstable_codegen macro causes them to not be used). I want to avoid "using" them because the changes would be untested. Of course, the compiler will let us know what variables have to be corrected when we restore them.

@adpaco-aws
Copy link
Contributor Author

Looks reasonable to me, Adrian. Do we have a ticket to track re-enabling these intrinsics at some point?

We didn't, but made one: #1148 . Thanks!

@adpaco-aws adpaco-aws merged commit 993b847 into model-checking:main May 3, 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.

3 participants