I have icui18n.dll and icuuc.dll. I don't seem to find icudt.dll from my
build output. Is that something that comes with v8?
On Monday, February 29, 2016 at 12:31:03 AM UTC-8, Jochen Eisinger wrote:
>
> I suspect that your binary can't find the icudt.dll file. InitializeICU()
> attempts to Loa
Umh, okay, thanks a lot!
Maybe I should elaborate my problem, hopefully I get some further help:
I (more or less with the help of a colleague) patched parts of the v8 code
(mostly the *String*) and added a few functions to the String prototype.
Let's call one of the function *isPatched(), *whic
--nouse-ic (which is equivalent to changing the flag's default and
recompiling) turns off those parts of the IC system that can reasonably be
turned off (in particular, compilation of specialized handlers). You'll
observe that --trace-ic's output changes quite a bit when you do that.
Turning off a
On Mon, Feb 29, 2016 at 9:31 PM, Scott Hulbert wrote:
> Jakob, here is a reproducible example (
> https://github.com/hulbert/bookshelf-sample-v8). I’m running this with
> node 5.6.0 on OS X (10.10.4).
>
That example explains a lot. Here, you're using "for (let virtualName in
virtuals) {", wherea
Hello,
I am using v8 4.5.103.30 and trying to disable inline-caching. I changed
the *use_ic *in src/flag-definitions.h to false and compiled v8.
Then I started d8 with the --trace-ic flag and kind of expected to not have
any IC's there (as the use of IC is disabled).
Am I right with that assum
