paritytech / paritytech/revive
resolc fails on deploy-only Yul objects
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 102
- Forks
- 26
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 6
Description
resolc --yul fails when a Yul object has no _deployed sub-object, while solc compiles it fine.
object "Test" {
code {
{ mstore(0, 42) return(0, 32) }
}
}
__runtime is created unconditionally even when no runtime code exists, leaving its entry block without a terminator.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the resolc --yul entry point and reproduce the failure with the deploy-only Yul object shown in the issue. Trace creation of __runtime and verify that an object without a _deployed sub-object compiles successfully, matching solc behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, solidity
- Domain
- blockchain, compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100