Fix expression type for a generated "!="-expression #49
Conversation
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
keep some string for truncated integer constants
keep some string for truncated integer constants
fix for OCaml 4.06.0 (-safe-string is the default)
how did opam compile this before?
missing fixes for 4.06
Newer versions return a single digit version number causing Cilly to fail. Copied over from sosy-lab/crest@512de07
Move happened in 62802fd
In perl v5.22, using '{' w/o escaping in a regex was deprecated, since v5.26 it is a syntax error
By adapting test script to use zarith (see 9d8e68e)
Test case combine21 is ok in GNU90-C, but invalid in GNU11. GNU90 used to be the default. Since GCC 5.1.0., default is GNU11, causing problems when using a newer GCC.
I don't know why `opam switch create .` chose ocaml 4.10.0. Upgrade to 4.11.1?
…ng representation is created in kintegerCilint.
* Use unthreaded version of Batteries * Use batteries.unthreaded in syntacticsearch * Add minimum version requirement for batteries
Fix infinite recursion in syntactic search
Remove unmaintained extensions
Remove varnameMapping from `cabs2cil`
Under OCaml 4.08.1 on Ubuntu Linux 20.04.2 LTS, running cilly gives this error message: $ cilly No arguments passed Usage: cilly [options] [gcc_or_mscl arguments] ... All other arguments starting with -- are passed to the Cilly process. The following are the arguments of the Cilly process Error: findlib: package loop for goblint-cil.makecfg. Fatal error: exception Errormsg.Error This patch fixes this problem.
Fix "package loop for goblint-cil.makecfg" error on OCaml 4.08.1
A "!=" expression must have type int.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes issue #29.