Summary: | [WinCE][V8]document.write(i) broken on 3rd loop on WebKit's WinCE port integrated with V8 JIT engine | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Chen Zhixiang <chenzx> | ||||
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED WONTFIX | ||||||
Severity: | Blocker | CC: | paroga | ||||
Priority: | P5 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Other | ||||||
OS: | Other | ||||||
Attachments: |
|
Description
Chen Zhixiang
2013-01-09 19:37:38 PST
Do you know if it is a V8 or WebKit problem? Does the same code work in the v8 shell? We now doubt it's the `OEMCacheRangeFlush` problem. JIT engine always accquires this API, but we are now using `FlushInstructionCache` from winbase.h. Don't know if WinCE 6.0 emulator implements the same behavior in `OEMCacheRangeFlush` and `FlushInstructionCache`. V8 Shell has no such problem, for it can't use `document.write`. If it is a webkit problem, why does the first 2 loop `document.write` success? I've used 3 kinds of loop: for、while、tail-recursive-call, all the same result. We are using a customed PB build for which we can't link to `OEMCacheRangeFlush` API, so I hesitate this may be the reason of problem. QtWebKit guys recently seems to having solved this problem, By disable inline cache fast path? https://codereview.qt-project.org/#change,45152 Closing since V8 won't be supported with WebKit any more. |