Comment #1 on issue 3645 by [email protected]: MSan vs. Serializer:
Fight!
https://code.google.com/p/v8/issues/detail?id=3645
Please CC [email protected] as well.
Ideally, mksnapshot would be allowed to serialize anything, but serialize
MSan's metadata along with it, so that after snapshot extraction, we'd
still know which bytes are uninitialized. This is probably hard.
It's not that hard if you're ok with losing origins (i.e. you will be able
to trace uninitialized data back to the deserializer, but not further). You
just need to ask MSan which memory is uninitialized during serialization,
and then mark it as uninitialized during extraction. The rest can be done
on the V8 side. MSan already has interface functions for both of those
tasks. The only problem is that those functions have byte-level precision,
whereas MSan has bit-level precision. But I'm sure we can add bit-level
interface if you decide to pursue this route.
I'm not really familiar with snapshotting. Does this scenario actually come
up in any non-trivial testing?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
