-
Notifications
You must be signed in to change notification settings - Fork 319
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
Ensure that hashing across account data and resize area works #3889
base: master
Are you sure you want to change the base?
Conversation
The Firedancer team maintains a line-for-line reimplementation of the |
d5f28a1
to
0434fc2
Compare
n_bytes: u64, | ||
accounts: &[SerializedAccountMetadata], | ||
memory_mapping: &MemoryMapping, | ||
mut fun: F, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be a &mut dyn FnMut
, instead of a generic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want &mut dyn FnMut
?
- It's such a short function, code bloat shouldn't be an issue (I think)
fn iter_memory_pair_chunks()
is also generic (so then both should be changed)
generic is "better inlining and optimization, but larger code" and dyn
is "shorter slower code, indirect calling is expensive and fewer optimizations possible".
wdyt?
c0c65ac
to
391319f
Compare
Problem
The account data consists of two areas: the orignal account data and the resize area, for when the account size is increased. Hashing across these two regions does not work, since they are distinct regions.
This change is required for direct mapping.
See stricter VM verfication SIMD