[webkit-dev] WebKit on MIPS: Nix port?
Dear WebKit Developers, With the departure of the Qt port, we are now actively looking for a primary port for using on MIPS. We are currently considering the Nix port, which is currently being merged into WebKit trunk. If you are using WebKit on MIPS with a different port in WebKit trunk (e.g. GTK or EFL), please contact us. Of course, we still support QtWebKit on MIPS outside of WebKit trunk, and plan to continue supporting it while QtWebKit is maintained. Best Regards, Gergely ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
Hi, On Sun, Jul 28, 2013 at 7:30 PM, Allan Sandfeld Jensen k...@carewolf.com wrote: became required in WebKit2. The only fallout will likely be the loss of the Qt MIPS bot which is maintained by a third party and is too old. The MIPS bot was updated to Debian Wheezy and GCC 4.7.2 a few weeks ago, I just forgot to update the buildbot slave info file, did it now. Best Regards, Gergely the 3rd party maintaining the MIPS bot :) ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] MIPS review requests
Dear WebKit Developers, Thank you for your support in getting LLINT for MIPS accepted into trunk. There are still a few patches that need review in order to get webkit trunk running on MIPS: 1. DFG JIT: https://bugs.webkit.org/show_bug.cgi?id=101328 We did the changes requested by the reviewers. Actually we did 2 versions of the patch so you can choose which one you like best. Unfortunately we did not get any reviews since then. 2. 64bit atomic implementation: https://bugs.webkit.org/show_bug.cgi?id=106739 We implemented 64bit atomic increment and decrement using a mutex. Unfortunately on MIPS there is currently no better solution. The same solution is used on Android as well. Unfortunately we did not get any more reviews on this issue either. 3. We also have another pending patch, which is not MIPS specific, but a fix to the style checker which should help anyone who is submitting patches with asm() statements: https://bugs.webkit.org/show_bug.cgi?id=101367 This patch has also attracted no review comments so far. Could anyone please help us in getting these patches reviewed, and (hopefully) accepted into webkit trunk? Thank you, Gergely ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Review Request: MIPS patches for LLINT and DFG
Dear Webkit Developers, We submitted MIPS implementations for LLINT and the DFG JIT. We also kept the patches rebased as the webkit-trunk moved forward, the latest update of the patches were uploaded today. 1. LLINT: https://bugs.webkit.org/show_bug.cgi?id=99706 Filip Pizlo was very helpful with refactoring LLINT to better accommodate the different RISC-like architectures. The latest versions of this patch already use this new infrastructure of the offline assembler (risc.rb). 2. DFG JIT: https://bugs.webkit.org/show_bug.cgi?id=101328 We also implemented the DFG JIT for MIPS. However, unfortunately we did not receive any review comments for it yet. 3. We also have another pending patch, which is not MIPS specific, but a fix to the style checker which should help anyone who is submitting patches with asm() statements: https://bugs.webkit.org/show_bug.cgi?id=101367 This patch has also attracted no review comments so far. Could anyone please help us in getting these patches reviewed, and (hopefully) accepted into webkit trunk? Please let us know if we are not properly following the contribution process. Thank you for your support, Gergely ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Github vs. git.webkit.org
Hi, Actually we already made the transition to the current github commit ids, because github wanted to shut down our repository, if it is not a fork of the semi-official webkit repository. Of course we will be able to transition back to the git.webkit.org commit ids, when the transition was made. I am just mentioning this, that you don't have to rush anything because of us. Best Regards, Gergely On Thu, Nov 29, 2012 at 3:53 PM, Jesus Sanchez-Palencia je...@webkit.orgwrote: 2012/11/28 Adam Barth aba...@webkit.org: My sense is that the WebKit community would prefer that the hashes in GitHub match the hashes in git.webkit.org so that folks can more easily move branches between the two. For my part, I've switched over to using GitHub exclusive of git.webkit.org, so the the difference in hashes aren't an issue for me, but I can understand why they'd be problematic for other people. After the force-push, would you still be able to push updates automatically? If so, you can switch the hashes whenever is convenient for you. (It might be nice to announce the date/time on this list so that folks aren't taken by surprise.) Thanks for letting us use your mirror. I've found it very useful to be able to push work-in-progress branches to GitHub to share with folks. +1. If we are all set about this, it would be awesome if we could move on with it, Tor Arne! This would also avoid some extra work for Gergely Kis, I guess... cheers, jesus ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Github vs. git.webkit.org
Hi, It looks like that the github mirror and git.webkit.org still has different SHA ids for commits. Is this final, or is the plan still to switch to the git.webkit.org SHA ids? For our MIPS staging repository we created a new mirror on github from git.webkit.org, and now we were asked by the github admins to reduce the repository to less than 1GB. I assume that if we would fork from the github.com/WebKit/webkit repository, then it would be fine with the github admins. However, if it is still the plan to switch to the git.webkit.org SHA ids in the github mirror as well, then we would like to avoid the extra work of rebasing our work to the github mirror commits, and then rebasing it back when the transition is made. We have to decide in the next couple days, because github will disable access to our repository again, so any status update on this transition plan would be helpful. Alternatively, if you have any experience with the github admins in how to ask for more space for webkit repositories, any advice would be very appreciated. Best Regards, Gergely Kis ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] MIPS port status update
Dear WebKit Developers, A quick status update on the MIPS port progress: - we have a build-only buildslave running ( http://build.webkit.org/builders/Qt%20Linux%20MIPS32R2%20LE%20Release/) (it is currently failing, a patch was already submitted to: https://bugs.webkit.org/show_bug.cgi?id=98856) - we have DFG and LLINT working for MIPS. We are going to start sending in the patches today or tomorrow. We plan to submit the work in 3 parts, as 3 separate issues in bugzilla: - common parts, which are used by both LLINT and DFG - LLINT MIPS implementation - DFG MIPS implementation Should we CC someone directly on these bugs to make the reviews easier? - Our porting effort uses the following git repository as a staging area: https://github.com/paul99/webkit The master branch in this repository is a direct mirror of the main webkit.org trunk branch. With the mips-master branch we are tracking the master branch, but also add a few MIPS specific patches that we are preparing for submitting back to the main webkit repository. Once we get LLINT and DFG accepted, the difference between the webkit trunk and our mips-master branch will be minimal: just the patches that were not yet accepted to webkit trunk. No forking or added exclusive features are intended here in this repository. We are committed to submit all MIPS support patches to the webkit.org main repository. Best Regards, Gergely ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] SH4, MIPS, and legacy-ARM assemblers in JavaScriptCore
Hi, Just wanted to note, that there is a working MIPS buildslave again: http://build.webkit.org/buildslaves/mips-1 It only does builds, no tests yet, we are working on that. Thank you everyone for your help! Unfortunately, the MIPS build is still red, because the following patch was not yet accepted to trunk (we bounced off of the commit bot the first time because the patch was malformed, but the current one should be fine now): https://bugs.webkit.org/show_bug.cgi?id=97243 We also have a MIPS DFG and LLINT implementation which passes the JSC testsuite and common benchmark suits (sunspider, v8). We are working on cleaning them up for submission. Best Regards, Gergely On Fri, Sep 14, 2012 at 3:01 AM, Gergely Kis gerg...@homejinni.com wrote: Hi, Submitted the patch for enabling the MIPS slave in build.webkit.org. https://bugs.webkit.org/show_bug.cgi?id=96713 Who should I send the buildbot password for the slave? Thanks, Gergely On Thu, Aug 30, 2012 at 9:52 AM, Holger Freyther ze...@selfish.orgwrote: On 08/30/2012 12:10 AM, Gergely Kis wrote: Would this be acceptable for you? sure, an actively and publicly maintained MIPS build would be great. We have some documentation on how to setup a build slave in the wiki[1] and the slave configuration files are maintained in SVN[2]. The configuration file changes follow the normal WebKit contribution procedure. holger [1] http://trac.webkit.org/wiki/BuildBot [2] http://trac.webkit.org/browser/trunk/Tools/BuildSlaveSupport/build.webkit.org-config ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] SH4, MIPS, and legacy-ARM assemblers in JavaScriptCore
Hi, Submitted the patch for enabling the MIPS slave in build.webkit.org. https://bugs.webkit.org/show_bug.cgi?id=96713 Who should I send the buildbot password for the slave? Thanks, Gergely On Thu, Aug 30, 2012 at 9:52 AM, Holger Freyther ze...@selfish.org wrote: On 08/30/2012 12:10 AM, Gergely Kis wrote: Would this be acceptable for you? sure, an actively and publicly maintained MIPS build would be great. We have some documentation on how to setup a build slave in the wiki[1] and the slave configuration files are maintained in SVN[2]. The configuration file changes follow the normal WebKit contribution procedure. holger [1] http://trac.webkit.org/wiki/BuildBot [2] http://trac.webkit.org/browser/trunk/Tools/BuildSlaveSupport/build.webkit.org-config ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] SH4, MIPS, and legacy-ARM assemblers in JavaScriptCore
Hi All, We are working on updating WebKit MIPS support. In particular we have a work in progress LLINT and DFG implementation for MIPS. We already have results (mozilla testsuite, sunspider and v8 benchmarks run reasonably well), but there are still some bugs that need to be fixed before we can submit this work. Regarding https://bugs.webkit.org/show_bug.cgi?id=79040, feel free to contact us if you need help with the MIPS specific bits. Regarding the MIPS buildbots: I will check internally if we can host a MIPS build slave (possibly including different boards) for the webkit project, and get back to you. Best Regards, Gergely On Wed, Aug 29, 2012 at 12:35 PM, Osztrogonac Csaba o...@inf.u-szeged.huwrote: Hi All, I'd like to inquire about the future of MIPS and SH4 assemblers. A long time ago we had buildbots for MIPS and SH4 platforms (hosted by Holger). But their last builds were at 29th June, machine were stopped, bots were removed from build.webkit.org (2 months before!). Is there anyone interested in maintaining MIPS and SH4 buildbots (and probably EWS bots) to catch build failures early? Gábor is working on fixing https://bugs.webkit.org/show_**bug.cgi?id=79040https://bugs.webkit.org/show_bug.cgi?id=79040and it seems the fix will affect all assemblers. But I don't think if it is a good idea to try to fix MIPS and SH4 assemblers blindly without EWS and buildbots. And who knows if MIPS and SH4 builds work now or not? br, Ossy Filip Pizlo írta: Hi all, We are actively trying to improve the WebKit JavaScript engine (JavaScriptCore), with new debugging, profiling, memory efficiency, and performance features. Because JavaScriptCore is a JIT-based engine, this inevitably means doing JIT work, which in turn includes adding new instructions to the JIT assemblers and changing the API between the assemblers and the JIT. Currently, the maintenance situation in the assembler layer is not great. We have three well-supported assemblers, X86-32, X86-64, and ARMv7. Then we have three assemblers that appear to be on life support: legacy (non-THUMB2, pre-v7) ARM, SH4, and MIPS. It is increasingly painful to maintain these three barely-supported assemblers. None of these assemblers has been updated to support the new JIT or interpreter infrastructure, and there appears to be no ongoing effort to do so. That means that for progress to be made on X86 and ARMv7, we need to increasingly scatter #if ENABLE(...) noise throughout the system to keep those other assemblers building. Neither the active JavaScriptCore contributors, nor those running the bots for those hardware platforms, appear to have much interest in maintaining those assemblers, other than the occasional build fix. This is not a good situation to be in. So, I am curious: is anyone shipping with the legacy ARM assembler, the MIPS assembler, or the SH4 assembler? As a secondary question, if you are shipping the legacy ARM assembler, are you doing so because you have legacy ARM hardware or because you have not had the chance to switch to the new ARM assembler in your codebase? -Filip __**_ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/**mailman/listinfo/webkit-devhttp://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] SH4, MIPS, and legacy-ARM assemblers in JavaScriptCore
On Wed, Aug 29, 2012 at 11:34 PM, Fu, Chao-Ying f...@mips.com wrote: On Wed, Aug 29, 2012 at 05:58:10PM +, Fu, Chao-Ying wrote: Hi All, Before a MIPS buildbot is ready, you can go ahead to change the assembler or any parts of code. We (MIPS) will test new code and submit patches that are required to fix the MIPS JSC build. Don't need to worry about breaking the MIPS build. (I have a cron job that checks out code and builds JSC on a native MIPS Linux every night.) This is the current process that we use, I think. Thanks a lot! Hi, more pennies. That is not how the other stakeholders develop inside the WebKit project. There is little to no value for this community if you test behind closed doors. E.g. how can members of this community know that a lack of communication is the lack of issues and not you being reassigned to something else? holger Sure. Will having new MIPS buildbot help to solve this concern? If yes, then you should not worry because we promise to help on buildbot. Thanks! Regards, Chao-ying Hi Holger, We are working together with MIPS to update and maintain the MIPS port of Webkit. We are setting up a buildbot slave to be integrated with build.webkit.org. First, it will use qemu emulation to run the on-target tests. However, this is only a temporary measure until we get at least one board dedicated to this purpose, then our slave will also execute tests on actual hardware. It is our current plan to have the initial qemu-only slave set up by next week. Should we contact you directly or someone else to get the slave integrated with build.webkit.org? Would this be acceptable for you? Best Regards, Gergely ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
