ETHGlobal

🧠 SOLIDITY INTERNALS

 
We will Deep Dive into Compiler, Storage, and Function Calls.



Solidity is known for helping developers abstract away the complexity of the #Ethereum Virtual Machine (EVM), 



For advanced developers, 

it is very important to understand what happens under the hood.

🧩 COMPILER BEHAVIOUR 

A Concise Study for advanced Devs


Today, we will look at an overview of the Solidity compiler pipeline (source → AST → IR → EVM bytecode)



A Solidity Compiler is a tool that converts Smart contracts into Bytecode for EVM understanding.

Don't forget, understanding these behaviours can enhance writing of cheaper contracts.



Solidity compilation has multiple stages that transform source code into optimized EVM bytecode.



These stages are called Compilation Pipeline

🟦 AST Generation 

This stage parses Solidity into an Abstract Syntax Tree that represents structure, scopes, and types.


🟨 IR Generation 

This produces High-Level IR (HIR) and Low-Level IR (LLIR) for optimization and analysis

🟩 Yul Translation 

While this stage converts IR into Yul, a low-level, EVM-targeted intermediate language.



🟥 Optimization 

This stage applies OZIR and Yul Optimizer passes, constant folding, inlining, dead code elimination and many more.

🟪 Bytecode Emission

A Very crucial stage that translates optimized Yul into final EVM bytecode.



Tip: Use [solc --ir, --optimize or  --yul ] to inspect internals.