I would think that fixing the existing OOL constant pool implementation is
a lot
less work than implementing a new one.
I'm not sure whether the existing implementation should be kept if you end
up
deciding to do your own thing, but I would err on the side of caution and
keep
it. Ross tells me that the performance benefit isn't great right now, but
I'm
kind of hopeful that avoiding code patching altogether would be beneficial
on
some platforms. For that, we need three pieces as far as I'm aware: (1)
vector
ICs (work in progress), (2) OOLCP, (3) a non-patching code ageing mechanism.
https://codereview.chromium.org/882263003/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
