{"id":3385,"date":"2026-11-04T15:50:21","date_gmt":"2026-11-04T15:50:21","guid":{"rendered":"https:\/\/wyominginvest.com\/?p=3385"},"modified":"2026-11-04T15:50:21","modified_gmt":"2026-11-04T15:50:21","slug":"solidity-compiler-v0-8-35-released-with-erc-7201-comptime-builtin-and-experimental-ssa-cfg-code-generator-2","status":"publish","type":"post","link":"https:\/\/wyominginvest.com\/?p=3385","title":{"rendered":"Solidity Compiler v0.8.35 Released with ERC-7201 Comptime Builtin and Experimental SSA CFG Code Generator"},"content":{"rendered":"<p>The development team has officially announced the release of the Solidity Compiler version v0.8.35, bringing a robust set of new features, performance enhancements, and critical improvements to the Ethereum developer ecosystem. Building upon previous iterations and incorporating feedback from recent pre-releases, this update introduces the language&#8217;s very first compile-time builtin, a formalized framework for handling experimental features, an advanced SSA control-flow graph code generator designed to tackle long-standing compilation bottlenecks, and essential bug fixes for the Intermediate Representation (IR) pipeline. <\/p>\n<p>Among the standout additions in v0.8.35 is the introduction of the <code>erc7201<\/code> builtin function. This feature computes the base storage slot for an ERC-7201 namespaced storage layout directly from its namespace string. ERC-7201 has become an increasingly vital standard in the Ethereum ecosystem, formalizing the practice of placing a smart contract&#8217;s state behind a securely hashed namespace. This approach effectively prevents storage collisions in complex, upgradeable architectures such as proxy-based and diamond-style patterns. <\/p>\n<p>What makes the new <code>erc7201<\/code> builtin uniquely powerful is that it marks the arrival of the first true compile-time, or &quot;comptime,&quot; builtin in Solidity. Prior to this release, the compiler&#8217;s compile-time evaluator was strictly limited to arithmetic operations performed on rational number literals. While existing builtins like <code>keccak256<\/code> have long benefited from constant folding during the optimization stage\u2014yielding significant gas savings\u2014they lacked the type-system advantage of being usable within a comptime context like a storage layout specifier. <\/p>\n<p>With version 0.8.35, the result of the <code>erc7201<\/code> builtin can be deployed anywhere a comptime expression is strictly required, serving seamlessly as the base slot in a layout specifier or even as an array length. This development directly addresses limitations previously highlighted during the 0.8.31 release cycle, paving the way for a more capable and versatile comptime evaluator in future updates. Developers can now cleanly integrate this into contracts using the custom storage layout specifier syntax, combining structural safety with optimal runtime performance.<\/p>\n<p>Alongside language-level enhancements, the new release places heavy emphasis on formalizing how experimental features are exposed to developers. In past versions of the compiler, in-development features could occasionally be enabled through a fragmented mix of ad-hoc command-line flags and experimental pragma directives. This lack of uniformity meant that developers did not always have a clear, consistent way of knowing when they were opting into unstable functionality, and metadata signaling remained patchy.<\/p>\n<p>Version 0.8.35 introduces a dedicated and transparent process, fully detailed in the updated documentation for experimental mode. Utilizing any experimental feature now universally requires a new top-level <code>--experimental<\/code> flag on the command line, or the corresponding boolean <code>settings.experimental<\/code> field when passing Standard JSON input. Serving as a master toggle, <code>--experimental<\/code> does not activate any specific feature on its own, but it acts as a mandatory gatekeeper for per-feature flags or pragmas. <\/p>\n<p>Attempting to use experimental features without this master flag now triggers a hard error, ensuring that developers are fully aware when they are incorporating unreleased or unstable logic into their builds. This change reinforces the understanding that experimental features carry no long-term stability guarantees and may undergo breaking changes even during non-breaking compiler releases. Furthermore, compilation metadata in both JSON and CBOR formats now explicitly records whether experimental mode was active during the build, closing previous transparency gaps regarding unreleased environment targets.<\/p>\n<p>Perhaps the most significant architectural addition in v0.8.35 is the introduction of an experimental Static Single Assignment control-flow graph, or SSA CFG, code generator for the IR pipeline. This new EVM backend generates optimized bytecode directly from a program&#8217;s SSA-form control-flow graphs\u2014one per function\u2014utilizing a precomputed stack layout that the backend meticulously shuffles the EVM stack to match.<\/p>\n<p>For years, the IR pipeline has faced two persistent developer pain points: frustrating &quot;stack-too-deep&quot; errors and sluggish compilation times. According to recent developer surveys, stack-too-deep errors remain one of the most frequently cited hurdles in smart contract development, while compilation via IR has historically been slower than the legacy evmasm pipeline. The traditional Yul-to-EVM code transformation relies on heuristics that frequently struggle when handling deeply nested expressions and intricate control flow. <\/p>\n<p>By introducing an SSA-based backend, the compiler team is establishing a much stronger and more predictable foundation for stack scheduling and overall compilation performance. Although this code generator is still in its early experimental stages and is not yet enabled by default for <code>--via-ir<\/code>, it has been heavily exercised against the full external-contract semantic test suite across continuous integration pipelines. Developers wishing to test the new pipeline can enable it using the combination of <code>--experimental<\/code> and <code>--via-ssa-cfg<\/code> flags, or via corresponding settings in JSON configurations. Before this backend eventually replaces current defaults, it will undergo rigorous review, extensive fuzzing, and external auditing.<\/p>\n<p>The release also continues the systematic deprecation work initiated in version 0.8.31, shifting focus toward claiming identifiers that will be officially promoted to reserved keywords in the upcoming 0.9.0 release. While earlier deprecations primarily targeted the removal of outdated features, the current batch focuses entirely on namespace reservation. Solidity declarations utilizing identifiers such as <code>at<\/code>, <code>error<\/code>, <code>layout<\/code>, <code>leave<\/code>, <code>super<\/code>, <code>this<\/code>, or <code>transient<\/code> will now emit informative warnings. <\/p>\n<p>Within Yul, standalone or inline assembly environments will see <code>leave<\/code> transition into a strict keyword, while a variety of identifiers like <code>basefee<\/code>, <code>blobbasefee<\/code>, <code>blobhash<\/code>, <code>clz<\/code>, <code>mcopy<\/code>, <code>memoryguard<\/code>, <code>prevrandao<\/code>, <code>tload<\/code>, and <code>tstore<\/code> will become reserved Yul identifiers. Because these reserved names correspond to existing Yul builtins, keeping them unreserved for this long was an unusual artifact of the extended 0.8.x release cycle, bound by strict backward-compatibility policies. These compiler warnings give developers ample time to proactively rename affected declarations well before version 0.9.0 turns these warnings into hard compilation errors.<\/p>\n<p>On the bugfix front, version 0.8.35 resolves a subtle inconsistency within the IR pipeline concerning custom errors and gas-saving optimization flags. The <code>--revert-strings strip<\/code> option\u2014or <code>revertStrings: \"strip\"<\/code> in Standard JSON\u2014allows developers to compile smaller bytecode by stripping revert reason strings while preserving the underlying revert mechanics. However, the introduction of custom errors via <code>require(condition, CustomError(...))<\/code> created complications, as custom errors encode structured data rather than simple textual messages. <\/p>\n<p>Prior to this update, the IR pipeline mistakenly stripped the custom-error arguments of <code>require<\/code> statements alongside standard strings, resulting in failed transactions reverting with empty error data instead of the expected structured custom error. While the legacy evmasm pipeline handled this correctly, the discrepancy has now been resolved in v0.8.35, ensuring that structured custom errors within <code>require<\/code> statements are properly preserved across all compilation pipelines.<\/p>\n<p>Additionally, the release reorganizes the output selection for ethdebug to align more closely with standard compiler output conventions. The older flags <code>--ethdebug<\/code> and <code>--ethdebug-runtime<\/code> have been replaced by more granular options: <code>--ethdebug-resources<\/code>, <code>--ethdebug-compilation<\/code>, <code>--ethdebug-program<\/code>, and <code>--ethdebug-program-runtime<\/code>, with equivalent keys provided in Standard JSON input. These outputs no longer force a complete binary compilation, and ethdebug features remain strictly experimental, properly gated behind the new <code>--experimental<\/code> toggle.<\/p>\n<p>Developers looking to upgrade to Solidity v0.8.35 can find comprehensive installation instructions and downloadable binaries directly through the project&#8217;s official GitHub repository and documentation portal. Those compiling directly from source are advised to use the dedicated source tarball rather than automated GitHub archives to ensure build integrity.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The development team has officially announced the release of the Solidity Compiler version v0.8.35, bringing a robust set of new features, performance enhancements, and critical improvements to the Ethereum developer ecosystem. Building upon previous iterations and incorporating feedback from recent pre-releases, this update introduces the language&#8217;s very first compile-time builtin, a formalized framework for handling<\/p>\n","protected":false},"author":3,"featured_media":3384,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[366],"tags":[401,2407,406,1184,2406,2313,407,2014,5,400,402],"class_list":["post-3385","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-smart-contract-auditing","tag-auditing","tag-builtin","tag-code","tag-compiler","tag-comptime","tag-experimental","tag-generator","tag-released","tag-security","tag-smart-contracts","tag-solidity"],"_links":{"self":[{"href":"https:\/\/wyominginvest.com\/index.php?rest_route=\/wp\/v2\/posts\/3385","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wyominginvest.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wyominginvest.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wyominginvest.com\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/wyominginvest.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3385"}],"version-history":[{"count":0,"href":"https:\/\/wyominginvest.com\/index.php?rest_route=\/wp\/v2\/posts\/3385\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wyominginvest.com\/index.php?rest_route=\/wp\/v2\/media\/3384"}],"wp:attachment":[{"href":"https:\/\/wyominginvest.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3385"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wyominginvest.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3385"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wyominginvest.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}