Solc semantic tests for which we currently are not able to check equivalence (for two different codegen paths)
- Dominant language
- Haskell
- Stars
- 358
- Forks
- 79
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 6
Description
- [ ] `conversions/function_type_array_to_storage.sol` - `hevm` crashes with `Internal Error: counterexample contains buffers that are too large to be represented as a ByteString` -- we don't crash, but the issue remains.
- [ ] `smoke/arrays.sol`
- [ ] `smoke/fallback.sol` - The problem documented in #697
- [ ] `errors/using_structs.sol`
- [ ] `events/event_indexed_string.sol`
- [ ] `fallback/call_forward_bytes.sol`
- [ ] `freeFunctions/recursion.sol`
- [ ] `getters/struct_with_bytes_simple.sol`
- [ ] `immutable/use_scratch.sol` - `hevm: Internal Error: cannot analyze symbolic code`
- [ ] `inlineAssembly/inline_assembly_for.sol`
- [ ] `inlineAssembly/inline_assembly_recursion.sol`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running the listed Solc semantic tests, beginning with the cases that report the documented hevm crashes or reference #697. Compare the two codegen paths for each failing file and use the existing failure messages to identify what prevents equivalence checking. Done means the listed cases can be checked for equivalence without the reported crashes or unresolved failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100