Hi Levent - 

v8 at r10875 doesn't even build for me, so I cannot explain your 'slowdown'. 

That rev on trunk is version 3.9.13. If you move to 3.9.14 (r10894), which was 
pushed just 24 hours later, the mips port will build and run fine, and I 
verified that the performance is normal (running v8 standalone). There are very 
few changes between these revs, so I think you'd be safe.

But if you prefer you can use r10875, and manually merge r10885 and r10892 from 
bleeding edge.

Not sure if you know, but the mips port is contributed from outside. One effect 
of this is that 'stable' trunk releases from Google are unlikely to be stable 
for mips (given the time required to port, test, upstream and code-review our 
changes). So far, we have made no attempt to replicate each trunk revision on 
our independent repo.

We do stay in sync for release branches, since 3.7. I suggest that whenever you 
can, you move to the 3.9 release branch (now at version 3.9.24.11). It has 
significant performance improvement for mips, and we finally support snapshots.

There are still 3 known bugs in the mips port on 3.9, with fixes that should be 
landed in the next few days, but the branch is fully usable for mips today.

thanks,

paul

On Apr 11, 2012, at 1:59 AM, L.A wrote:

> Hi,
> 
> I am running a chromium based webkit port on mipsel linux. I have
> recently updated the codebase to 10875:
> 
>    http://src.chromium.org/viewvc/chrome/releases/19.0.1068.0/DEPS?view=markup
> 
> I was previously running a code base from Oct2011. For some reason
> with the new codebase, javascript slowed down by a factor of 100 (ex:
> v8 benchmark suite). I am not very familiar with v8, so I thought
> maybe someone might give me some pointers/ideas to attack this. One
> (hopefully relevant) datapoint:
> 
> When running the v8 suite, if I stop the browser, the first resolved
> function in the stack is usually one of these three:
> v8::internal::LoadIC_Miss, v8::internal::CallIC_Miss,
> v8::internal::Runtime::PerformGC
> 
> Thanks,
> Levent
> 
> 
> =========================
> PS: these are my compile options:
> 
> '-D_FILE_OFFSET_BITS=64' '-DNO_TCMALLOC' '-DCHROMIUM_BUILD' '-
> DWEBUI_TASK_MANAGER=1' '-DENABLE_WEBRTC=1' '-
> DENABLE_CONFIGURATION_POLICY' '-DENABLE_INPUT_SPEECH' '-
> DENABLE_NOTIFICATIONS' '-DENABLE_GPU=1' '-DUSE_OPENSSL=1' '-
> DENABLE_EGLIMAGE=1' '-DUSE_SKIA=1' '-
> DENABLE_REGISTER_PROTOCOL_HANDLER=1' '-DENABLE_WEB_INTENTS=1' '-
> DENABLE_PLUGIN_INSTALLATION=1' '-DENABLE_DEBUGGER_SUPPORT' '-
> DV8_TARGET_ARCH_MIPS' '-DCAN_USE_FPU_INSTRUCTIONS' '-
> D__mips_hard_float=1' '-DNDEBUG' '-DNVALGRIND' '-
> DDYNAMIC_ANNOTATIONS_ENABLED=0' -Iv8/src  -pthread -fno-exceptions -
> fno-strict-aliasing -Wno-unused-parameter -Wno-missing-field-
> initializers -fvisibility=hidden -pipe -fPIC -Wno-format -Wno-unused-
> result -EL -mhard-float -mips32 -Wa,-mips32 -fno-ident -fdata-sections
> -ffunction-sections -fdata-sections -ffunction-sections -fomit-frame-
> pointer -O3 -fpermissive -fno-rtti -fno-threadsafe-statics -
> fvisibility-inlines-hidden
> 
> -- 
> v8-users mailing list
> [email protected]
> http://groups.google.com/group/v8-users

-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users

Reply via email to