Skip to content
This repository was archived by the owner on Jul 5, 2024. It is now read-only.

Untrack last_callee_* of StepState#99

Merged
han0110 merged 1 commit into
privacy-ethereum:masterfrom
han0110:feature/untrack-last-callee-info
Jan 29, 2022
Merged

Untrack last_callee_* of StepState#99
han0110 merged 1 commit into
privacy-ethereum:masterfrom
han0110:feature/untrack-last-callee-info

Conversation

@han0110
Copy link
Copy Markdown
Contributor

@han0110 han0110 commented Jan 20, 2022

This PR is once part of #82, and aims to move the tracking of last_callee_* to rw_table for simplicity.

@han0110 han0110 mentioned this pull request Jan 20, 2022
1 task
Copy link
Copy Markdown
Collaborator

@ChihChengLiang ChihChengLiang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Contributor

@ed255 ed255 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Comment thread tests/evm/test_begin_tx.py Outdated
Comment on lines +161 to +163
(17, RW.Read, RWTableTag.CallContext, 1, CallContextFieldTag.LastCalleeId, 0, 0, 0),
(18, RW.Read, RWTableTag.CallContext, 1, CallContextFieldTag.LastCalleeReturnDataOffset, 0, 0, 0),
(19, RW.Read, RWTableTag.CallContext, 1, CallContextFieldTag.LastCalleeReturnDataLength, 0, 0, 0),
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current conflict comes because of #94
These tuples now have 10 elements, so they require 2 extra trailing zeroes.

@han0110 han0110 force-pushed the feature/untrack-last-callee-info branch from a4e7240 to 28827d1 Compare January 29, 2022 09:54
@han0110 han0110 merged commit d1f7672 into privacy-ethereum:master Jan 29, 2022
@han0110 han0110 deleted the feature/untrack-last-callee-info branch January 29, 2022 09:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants