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

Move storage syscalls to libtock-drivers #633

Merged
merged 1 commit into from
Jun 12, 2023

Conversation

kaczmarczyck
Copy link
Collaborator

Fixes #627

This PR is purely stylistic, and doesn't change any functionality.

@kaczmarczyck kaczmarczyck requested a review from ia0 June 12, 2023 16:21
@kaczmarczyck kaczmarczyck self-assigned this Jun 12, 2023
@kaczmarczyck kaczmarczyck linked an issue Jun 12, 2023 that may be closed by this pull request
@coveralls
Copy link

Coverage Status

coverage: 96.334%. remained the same when pulling 464ee09 on kaczmarczyck:storage-syscalls into e9ea05f on google:develop.

@kaczmarczyck kaczmarczyck merged commit 3813cac into google:develop Jun 12, 2023
@kaczmarczyck kaczmarczyck deleted the storage-syscalls branch June 12, 2023 21:50
let storage_ptr = memop::<S>(memop_nr::STORAGE_PTR, i)? as usize;
let storage_len = memop::<S>(memop_nr::STORAGE_LEN, i)? as usize;
let storage_ptr = to_storage_result(LibtockStorage::<S, C>::storage_ptr())?;
let storage_len = to_storage_result(LibtockStorage::<S, C>::storage_len())?;
Copy link
Member

Choose a reason for hiding this comment

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

This is actually a regression fixed by #637.

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.

Move storage syscalls
3 participants