DescriptionGeneration of our home-grown memmove doesn't depend on serializer state anymore.
The serializer state has to be per-Isolate, but at the point where we
generate our memmoves we don't really have an Isolate. Furthermore,
there was no fundamental reason why we shouldn't use our home-grown
memmove during mksnapshot time.
Perhaps we can totally remove our own memmove nowadays, but this would
be a separate CL.
BUG=359977
LOG=y
R=bmeurer@chromium.org
Committed: https://code.google.com/p/v8/source/detail?r=21116
Patch Set 1 #Patch Set 2 : Removed parameter. #
Messages
Total messages: 3 (0 generated)
|