feat: change TRM module to recognize secp256r1 prc address #1281
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.
Add new recognition of precompile address in
TRMmodule as per this issue Consensys/linea-specification#272From Osaka and on, a PRC address for curve secp256r1 has been added at address 0x100
In
trm.acceptsIS_PRECOMPILEup to address 0x11 (like in Prague)PLUS Fix of bit_xoan/signextend documentation
Note
Extend TRM precompile detection to
{0x1..0x11} ∪ {0x100}and tidy docs inbit_xoanandsignextend.testdata/asm/bench/trm.zkasm):MAX_PRC_CONTIGUOUS_ADDRESS = 0x11and detect0x100(secp256r1) as precompile.trmlogic to flag precompiles whenlow <= 0x11orlow == 0x100using boolean combine(b1 + b2) - (b1 * b2).testdata/asm/util/bit_xoan.zkasmandtestdata/asm/util/signextend.zkasm; reformat examples and instruction names.Written by Cursor Bugbot for commit 93899ef. This will update automatically on new commits. Configure here.