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.

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

Advanced goto-diff #40

Closed
peterschrammel opened this issue Mar 29, 2016 · 3 comments
Closed

Advanced goto-diff #40

peterschrammel opened this issue Mar 29, 2016 · 3 comments
Labels
research idea Static Analyses

Comments

@peterschrammel
Copy link
Member

syntactic and semantic diffing of goto programs
@peterschrammel peterschrammel self-assigned this Mar 29, 2016
@peterschrammel
Copy link
Member Author

basic syntactic diffing in pull request #65

@peterschrammel
Copy link
Member Author

integrate

  • deltacheck's change impact analysis
  • cemc equivalence checker

@peterschrammel peterschrammel changed the title goto-diff Advanced goto-diff Sep 11, 2018
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Feb 28, 2019
@JohnDumbell
Add global name map to goto_symex_state
4fa79ae 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Feb 28, 2019
@JohnDumbell
Add global name map to goto_symex_state
ed5acf1 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Feb 28, 2019
@JohnDumbell
Add global name map to goto_symex_state
d5df8b3 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 1, 2019
@JohnDumbell
Add global name map to goto_symex_state
1e28fff 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 1, 2019
@JohnDumbell
Add global name map to goto_symex_state
6b815c8 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 4, 2019
@JohnDumbell
Add global name map to goto_symex_state
e718a62 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
smowton pushed a commit to smowton/cbmc that referenced this issue Mar 7, 2019
@JohnDumbell @smowton
Add global name map to goto_symex_state
743bcd3 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
smowton pushed a commit to smowton/cbmc that referenced this issue Mar 7, 2019
@JohnDumbell @smowton
Add global name map to goto_symex_state
fc3dfc1 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
smowton pushed a commit to smowton/cbmc that referenced this issue Mar 7, 2019
@JohnDumbell @smowton
Add global name map to goto_symex_state
bc61313 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 8, 2019
@JohnDumbell
Add global name map to goto_symex_state
cf15471 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 12, 2019
@JohnDumbell
Add global name map to goto_symex_state
952ac25 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 12, 2019
@JohnDumbell
Add global name map to goto_symex_state
307d2b6 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 12, 2019
@JohnDumbell
Add global name map to goto_symex_state
64df4bb 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 12, 2019
@JohnDumbell
Add global name map to goto_symex_state
1413144 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 12, 2019
@JohnDumbell
Add global name map to goto_symex_state
974fefc 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
smowton pushed a commit to smowton/cbmc that referenced this issue Mar 13, 2019
@JohnDumbell @smowton
Add global name map to goto_symex_state
de168d4 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
smowton pushed a commit to smowton/cbmc that referenced this issue Mar 14, 2019
@JohnDumbell @smowton
Add global name map to goto_symex_state
253370e 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
smowton pushed a commit to smowton/cbmc that referenced this issue Mar 15, 2019
@JohnDumbell @smowton
Add global name map to goto_symex_state
ac2b5b7 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 15, 2019
@JohnDumbell
Add global name map to goto_symex_state
d5c50b7 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
JohnDumbell added a commit to JohnDumbell/cbmc that referenced this issue Mar 15, 2019
@JohnDumbell
Add global name map to goto_symex_state
131373b 
This global name map will be used to check what generation is currently
available for each level1 name, and shared across all states. This will
only be used when a particular state tries to find out what the next
free generation is.

The main draw of this is that all branches will now assign unique
generations that won't clash with assignments done across other
branches. One minor downside is that in VCC's the generation number
might jump sporadically (say from diffblue#4 to diffblue#40).
@peterschrammel peterschrammel removed their assignment Feb 6, 2021
@TGWDB TGWDB mentioned this issue Aug 10, 2021
Merged
7 tasks
@TGWDB
Copy link
Contributor

TGWDB commented Sep 1, 2021

Closing due to detail in #6284

@TGWDB TGWDB closed this as completed Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
research idea Static Analyses
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@peterschrammel @TGWDB