Solidity Version 0.8.39
- Version
v0.8.39- Repository
- ethereum/solidity
Release notes
We are excited to announce the release of the Solidity Compiler v0.8.39!
This release fixes a security bug that yields a storage corruption when overwriting (by copying) a recursive struct in storage with a struct nested inside it. In addition, we've also fixed some other smaller bugs, as well as continuing our work on the experimental Ethdebug features.
Changelog
Important Bugfixes:
• Code Generator: Fix storage corruption when overwriting a recursive struct in storage with a struct nested inside it. Copying a recursive struct between storage locations now performs a runtime overlap check, taking a memory snapshot of the source when the target contains it.
Compiler Features:
• Commandline Interface: Omit the compilation record from --ethdebug-resources (experimental).
• ethdebug: Populate the type and pointer tables of ethdebug/format/info/resources with type documents and layout-specific pointer templates for storage, transient storage, memory and calldata (experimental).
• ethdebug: Stamp the ethdebug/format/program and ethdebug/format/info/resources outputs with their schema and the version of the ethdebug/format specification they follow (experimental).
• EVM: Warn about exceeding the increased contract code size (64 KiB) and initcode size (128 KiB) limits instead of the EIP-170 and EIP-3860 limits when compiling for the Amsterdam EVM version (EIP-7954).
• Standard JSON Interface: Omit the compilation record from ethdebug.resources (experimental).
• Yul: Warn when the assembled bytecode of a compiled Yul object exceeds the EIP-170 (runtime code) or EIP-3860 (initcode) size limit, matching the existing warnings for Solidity input.
Bugfixes:
• Code Generator: Fix tuple assignments swapping values when a nested tuple component occupying at least one stack slot grows during type conversion.
• ethdebug: Fix incorrect source file IDs in instruction locations (experimental).
• SMTChecker: Fix empty tuples being printed as an undeclared constant in SMT-LIB queries, which made the solver reject every query of the affected contract.
• SMTChecker: Fix false negative in CHC engine when a function from abstract base is called externally using this.
We would especially like to thank all the contributors that made this release possible:
blishko, clonker, djole, Hugo de Sa Pereira Pinto, Kamil Śliwak, Mate Soos, Matheus Aguiar, Nikola Matić, r0qs, rodiazet