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

Bitfield Domain #1623

Draft
wants to merge 108 commits into
base: master
Choose a base branch
from
Draft

Bitfield Domain #1623

wants to merge 108 commits into from

Conversation

ManuelLerchner
Copy link

This pull request introduces a new bitfield domain, into the IntDomain.

Currently being worked on...

Copy link

@github-advanced-security github-advanced-security bot left a comment

Choose a reason for hiding this comment

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

Semgrep OSS found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

src/cdomain/value/cdomains/intDomain.ml Fixed Show fixed Hide fixed
src/cdomain/value/cdomains/intDomain.ml Fixed Show fixed Hide fixed
norm ik (z3, o3)

let neg ?no_ov ik x =
M.trace "bitfield" "neg";

Check warning

Code scanning / Semgrep OSS

Semgrep Finding: semgrep.trace-not-in-tracing Warning

trace functions should only be called if tracing is enabled at compile time
let lognot ik i1 = BArith.lognot i1 |> norm ik |> fst

let shift_right ik a b =
M.trace "bitfield" "shift_right";

Check warning

Code scanning / Semgrep OSS

Semgrep Finding: semgrep.trace-not-in-tracing Warning

trace functions should only be called if tracing is enabled at compile time
else norm ik (BArith.shift_right ik a b)

let shift_left ik a b =
M.trace "bitfield" "shift_left";

Check warning

Code scanning / Semgrep OSS

Semgrep Finding: semgrep.trace-not-in-tracing Warning

trace functions should only be called if tracing is enabled at compile time
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants