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
Introducing MemoryAccessor
for abstraction on memory access operations
#7515
Introducing MemoryAccessor
for abstraction on memory access operations
#7515
Conversation
* @param field | ||
* @return | ||
*/ | ||
long getObjectFieldOffset(Field field); |
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.
May be should javaDoc here ?
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.
ah, I have forgotten them
bab4fef
to
b21c67f
Compare
} | ||
|
||
@Override | ||
public long getLong(long address) { |
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.
Where I can point which ENDIAN here ?
3597e9f
to
464a1c3
Compare
*/ | ||
@Deprecated |
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.
Maybe you can note the reason of deprecation?
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.
ok
only minors comments. 👍 |
464a1c3
to
c2a390b
Compare
…ing-memory-accessor Introducing `MemoryAccessor` for abstraction on memory access operations
MemoryAccessor
is a new contact point for accessing memory.MemoryAccessor
implementations areUnsafe
based and interprets given addresses as native memory addresses. So these implementations can be thought as direct memory accessors.UnsafeHelper
is deprecated and offeredMemoryAccessor
instead.The follow-up task of this PR should be cleaning
Unsafe
usages in our code base.