Stashing in a spare field sounds ideal if possible. I'll have a look, but
do
you
have any candidates?
Logical way would be to share the "code" field and make it (code | bytecode)
field, which points
1) to code if there is no bytecode
2) to bytecode if there is no code
3) to pair (code, bytecode) if both are present. (do you expect this to be
common case?)
That probably requires some work. Not sure if it can regress perf.
Alternative is to find another field that is rarely used and share it with
bytecode, e.g. inferred_name, debug_info, counters. This sharing would be
somewhat arbitrary and hacky.
https://codereview.chromium.org/1230753004/
--
--
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.
