-
Notifications
You must be signed in to change notification settings - Fork 20
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
WIP: Hydai/update solility 0.5.12 #21
Draft
hydai
wants to merge
2,754
commits into
master
Choose a base branch
from
hydai/update-solility-0.5.12
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
+98,300
−24,353
Conversation
This file contains 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
[SMTChecker] Fix ICE when reporting cex
[SMTChecker] Relax expectations for complex nonlinear tests
Remove ubuntu cosmic (EOL July 18, 2019) from release script.
…ically-sized members.
[SMTChecker] Support StringLiteral type
Buglist entry for calldata structs with dynamically encoded, but statically-sized members.
Prepare changelog for release.
[SMTChecker] Add CHC constructor/interface/error blocks
Merge develop into release.
Remove version in errors for release build.
[DOCS] Change link in using compiler
YulInterpreter: Call functions with the correct context
Set version to 0.5.12.
Merge release back into develop.
Remove the shared Z3 build from the testing Dockerfile.
CMake: Properly disable z3, if z3 version cannot be determined.
[Trivial] Test scripts: Make build dir a variable
[YulOpt] Create SSA variable after control flow joins
solc fuzzer: Use randomly chosen evm version
ossfuzz: Create a separate cmake toolchain file for ossfuzz
Enable nightly tests for 0.6.0
I _believe_ (someone more knowledgable than I should verify this claim) that Solidity will always write out an `output` member. If there are no return parameters, then the array will be empty, but the `output` property will be present. If this is not correct, I will withdraw this PR, but if the assertion is correct then the docs should reflect that so people can rely on the `output` property being present when writing ABI processors. I also fixed some inconsistency in line termination character. It was sometimes `.` and sometimes `;`. I picked `.`, but don't really care which as long as it is consistent.
…lance Document chainid and selfbalance.
[SMTChecker] Add "as const: function to SMTLib2Interface
Fix error message about accessing storage pointers.
[SMTChecker] Fix SMT name for function identifiers
Refactor Optimiser Steps Interface.
…line terminators.
…-crlf Fixes doxygen style multiline comment parsing for files with CRLF
Fixes source location in warning for shadowing import delcarations.
Add clang build and test CIs
Removes the optionality on `output` in ABI docs.
Update changelog for 0.5.12 release.
Fix internal compiler error for arrays of recursive structs.
Merge develop into release for 0.5.12
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.
Checklist