-
Notifications
You must be signed in to change notification settings - Fork 83
Refactor writing to pointers #1531
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
Draft
karoliineh
wants to merge
9
commits into
master
Choose a base branch
from
base_set_fold
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
9485208
Remove deadcode that catches `SetDomain.Unsupported`
karoliineh 65e1ccc
Replace complicated set logic with simplified AD.fold
karoliineh 87a979a
Make update_one case handling explicit
karoliineh c4d96e8
Assert that the set of lvals is not empty when written to
karoliineh c7199a0
Do not remove NullPtr-s from address sets
karoliineh 7816bed
Add stdlib.h for correctly importing strtol
karoliineh 7d87b35
Fix `17-per_elem_simp`: nowarn -> norace
karoliineh a30fbfc
Do not remove `UnknownPtr` from address set before running `reachable…
karoliineh 6843784
Use `sem.null-pointer.dereference` option for writing as well
karoliineh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,6 +2,7 @@ | |
#include<goblint.h> | ||
#include <wchar.h> | ||
#include <stdio.h> | ||
#include <stdlib.h> | ||
|
||
int g = 8; | ||
|
||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding something I noticed in #1777 (comment): this now makes writing to
NULL
more explicit, but somehow there's still no warning.I'm now wondering if we're actually missing a warning here or we actually emit one from somewhere else already. Should probably figure this out while we're at it.