Cfg choose create analysis, option on bytecode size limit #210
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
This was referenced Feb 8, 2024
Merged
This was referenced Feb 16, 2024
Closed
Merged
This was referenced Feb 24, 2024
Merged
This was referenced Mar 8, 2024
Merged
This was referenced Mar 22, 2024
Closed
Closed
Closed
This was referenced Mar 26, 2024
Merged
This was referenced Apr 2, 2024
Merged
This was referenced Apr 16, 2024
This was referenced May 2, 2024
Closed
This was referenced May 13, 2024
Closed
Closed
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow to configure if created bytecode is going to by analysed, checked or saved as raw code. By default it will be analysed, only time when this becomes relevant is when you want to switch between forks as analysis takes into account what spec is currently using and it is different from spec to spec.
In future we will probably add spec friendly analysis with only jump table and without gas blocks.
One more small change is around making cfg perf bytecode limit as
Optionif not set consensus value would be used.