Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LDC support in predicates #612

Merged
merged 11 commits into from
Oct 23, 2024
Merged

LDC support in predicates #612

merged 11 commits into from
Oct 23, 2024

Conversation

Dentosal
Copy link
Member

@Dentosal Dentosal commented Oct 6, 2024

Closes #456

Requires #611
VM PR FuelLabs/fuel-vm#848

Before requesting review

  • I have reviewed the code myself

@Dentosal Dentosal self-assigned this Oct 6, 2024
Copy link
Contributor

@xgreenx xgreenx left a comment

Choose a reason for hiding this comment

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

LGTM=) @Voxelot What do you think?

Comment on lines +145 to 149
### Call

Call context is entered via [`CALL` instruction](./instruction-set.md#call-call-contract). It's also called _internal context_, or _contract context_. Call context is used to access state of a contract.

## Call Frames
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe it is better to do like this?

Suggested change
### Call
Call context is entered via [`CALL` instruction](./instruction-set.md#call-call-contract). It's also called _internal context_, or _contract context_. Call context is used to access state of a contract.
## Call Frames
## Call
Call context is entered via [`CALL` instruction](./instruction-set.md#call-call-contract). It's also called _internal context_, or _contract context_. Call context is used to access state of a contract.
### Call Frames

Copy link
Member Author

Choose a reason for hiding this comment

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

No. Call is a subheader of Contexts.


During predicate mode, hitting any [contract instruction](./instruction-set.md#contract-instructions) causes predicate verification to halt, returning Boolean `false`.
During predicate mode, hitting any [contract instruction](./instruction-set.md#contract-instructions) (except `ldc` with non-contract target) causes predicate verification to halt, returning Boolean `false`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, it looks like before we should allow usage of blob instructions in the VM as well(because they are not contract instruction)=D So now it works as expected

Base automatically changed from dento/ldc-mode-2 to master October 15, 2024 13:37
@Dentosal Dentosal marked this pull request as ready for review October 15, 2024 15:15
@Dentosal Dentosal requested review from xgreenx and a team October 15, 2024 16:08
@Dentosal Dentosal merged commit 6d91f86 into master Oct 23, 2024
6 checks passed
@Dentosal Dentosal deleted the dento/predicate-relax-limits branch October 23, 2024 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LDC support in predicate feature
3 participants