Daniel
Daniel
Part of investigating https://github.com/ethereum/solidity/issues/13224 and to confirm that the issue is still there, since I'm having trouble reproducing it locally, and if the compiler injection works properly for current ENS...
First step in https://github.com/ethereum/solidity/issues/13323. Previously, we considered adding a ``code`` data location - however, since EOF will have an actual data section, ``code`` as keyword may actually be misleading. So...
Depends on https://github.com/ethereum/solidity/issues/13368. As a second step of https://github.com/ethereum/solidity/issues/13323, we properly type check the new ``code`` data location. This entails removing the syntax error introduced in https://github.com/ethereum/solidity/issues/13368 and instead implementing...
Currently, the Solidity AST is ``const`` after parsing and then ``annotation()``-annotated by the analysis steps in ``CompilerStack::analyze``. However, some AST nodes and some Types have interfaces that implicitly depend on...
The CSE run at the very end after the stack compressor actively causes problems in https://github.com/ethereum/solidity/issues/9622 So maybe we should think about making the hard-coded part of the sequence ``suite.runSequence("fDnTOc...
We trigger PPA release builds for the upcoming Ubuntu release as early failure indicator and in the last release it actually failed: https://launchpadlibrarian.net/617180489/buildlog_ubuntu-kinetic-amd64.solc_1%3A0.8.16-0ubuntu1~kinetic_BUILDING.txt.gz We should check with a ubuntu 22.10...
We add a lot of compiler flags that make the builds as strict and pedantic as possible. While that's very good for our development and CI, this can be annoying...
For reference: https://discuss.circleci.com/t/march-2022-support-for-new-operating-system-for-windows-executors-windows-server-2022/43198 and https://circleci.com/docs/2.0/hello-world-windows/#windows-executor-images
Nothing fancy, but a few gas here and there... Kind of depends on https://github.com/ethereum/solidity/issues/12913, but wouldn't be fatal to merge without.
We specifically compile ``soljson.js`` with ``WASM_ASYNC_COMPILATION=0`` - there was a reason for this, but I don't remember right now. However, I think at least chromium-based browsers won't allow synchronous compilation...