mirror of https://github.com/ethereum/solidity synced 2023-10-03 13:03:40 +00:00

Files

T

Kamil Śliwak 3c7112ed2b Remove the assertion against functions bound to types for which should not be possible

- The list was wrong - we do support string and int literals
- The assertion was meant to guard against silently skipping over types for which there is no special handling. The current code handles everything in a generic way though and likely will not have to be adjusted for newly added types so the risk of that happening is low.

2021-06-02 13:59:42 +02:00

Common.cpp

Extract referencedDeclaration as helper.

2021-03-24 17:01:50 +01:00

Common.h

Extract referencedDeclaration as helper.

2021-03-24 17:01:50 +01:00

IRGenerationContext.cpp

Respect memory model for revert.

2021-05-03 18:23:41 +02:00

IRGenerationContext.h

Respect memory model for revert.

2021-05-03 18:23:41 +02:00

IRGenerator.cpp

Document the panic function of library deployment

2021-05-26 15:51:46 +01:00

IRGenerator.h

Remove IRGenerator::verifyCallGraphs and make generate() verify the graphs automatically

2021-02-23 10:47:02 +01:00

IRGeneratorForStatements.cpp

Remove the assertion against functions bound to types for which should not be possible

2021-06-02 13:59:42 +02:00

IRGeneratorForStatements.h

Respect memory model in forwarding revert inside catch.

2021-05-03 12:19:46 +02:00

IRLValue.h

Add SPDX license identifier if not present already in source file

2020-07-17 20:24:12 +05:30

IRVariable.cpp

Replaced boost::adaptors::transformed

2021-04-08 17:38:14 +05:30

IRVariable.h

[Sol->Yul] Enabling storage pointers to local vars in inline assembly.

2020-08-26 10:25:42 +02:00

README.md

Document differences between legacy Solidity and Solidity via Yul.

2019-07-11 17:48:06 +02:00

README.md

The Solidity to Yul Code Generator

This directory contains the new experimental code generator that compiles Solidity to an intermediate representation in Yul with EVM dialect.

The main semantic differences to the legacy code generator are the following:

Arithmetic operations cause a failing assertion if the result is not in range.
Resizing a storage array to a length larger than 2**64 causes a failing assertion.