Re: [webkit-dev] Youenn Fablet is now a WebKit reviewer

2015-10-27 Thread youenn fablet
Thanks everybody! Diving into WebKit is a great experience :) y Le mar. 27 oct. 2015 à 13:03, SaamBarati1 a écrit : > Congrats! > > > Saam > > > > > On Oct 26, 2015, at 7:15 PM, Mark Lam wrote: > > > > Hello everyone, > > > > I would like to

Re: [webkit-dev] Webkit JavaScript interpreter crash (v. 153112/ppc64le).

2015-10-27 Thread Atul Sowani
I tried with JSC_useJIT=0 as well as with JSC_useLLInt=0, however that did not help. The crash is still happening. First there was an error about page alignment, which I bypassed. Now the program hangs in dtoa() --> mult(). One doubt: wouldn't dtoa code (in dtoa.cpp/.h) need specific porting for

Re: [webkit-dev] Youenn Fablet is now a WebKit reviewer

2015-10-27 Thread Xabier Rodríguez Calvar
Hi, O Lun, 26-10-2015 ás 19:15 -0700, Mark Lam escribiu: > Youenn, congratulations. Definitely, congratulations! signature.asc Description: This is a digitally signed message part ___ webkit-dev mailing list webkit-dev@lists.webkit.org

Re: [webkit-dev] Webkit JavaScript interpreter crash (v. 153112/ppc64le).

2015-10-27 Thread Filip Pizlo
Usually, making JSC work on a new platform requires a non-trivial engineering investment. I wouldn't expect any version of JSC to work on PPC out of the box. -Filip > On Oct 27, 2015, at 4:15 AM, Atul Sowani wrote: > > I tried with JSC_useJIT=0 as well as with

Re: [webkit-dev] Improved CrashLog collection in Webkit Tests

2015-10-27 Thread Simon Fraser
> On Oct 27, 2015, at 3:09 PM, Aakash Jain wrote: > > Hi All, > > In the webkit test results page, we have added a section "Other Crashes" > (through https://bugs.webkit.org/show_bug.cgi?id=150056). After the tests are > complete, we go through the crashlog directory on

[webkit-dev] Improved CrashLog collection in Webkit Tests

2015-10-27 Thread Aakash Jain
Hi All, In the webkit test results page, we have added a section "Other Crashes" (through https://bugs.webkit.org/show_bug.cgi?id=150056). After the tests are complete, we go through the crashlog directory on the machine and scan all the crashlogs generated during test run. We then check if