Re: [webkit-dev] SH4, MIPS, and legacy-ARM assemblers in JavaScriptCore

[Zoltan Herczeg]

Hi Filip,

we (Gabor Loki and me) are the maintainers of the traditional ARM port,
and we are willing to fix all issues. Just let us know what we need to do.
You can assign the necessary bug reports to us and we are available in the
#squirrelfish (or #webkit) channel as well.

Regards,
Zoltan

> 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.cgi/webkit-dev
>


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] SH4, MIPS, and legacy-ARM assemblers in JavaScriptCore

[Fu, Chao-Ying]

Hi Filip,

  We (MIPS Technologies) have customers that ship MIPS Qt WebKit and
Android that uses WebKit JSC.  Also, we are working on the new interpreter and 
the new JIT.
We think it would be ready in two months to contribute our code to webkit.org.

  We have a nightly cron job that checks out source code from webkit.org, 
built, run regression tests, and run SunSpider tests.  Also, I think there is
a buildbot for Qt Linux MIPS Release there.
http://trac.webkit.org/wiki/QtWebKitBuildBots

  If you need to add or change assembler APIs, please let me know and we will 
be very
happy to work on it from the MIPS side.  Thanks a lot!

Regards,
Chao-ying


> -Original Message-
> From: webkit-dev-boun...@lists.webkit.org 
> [mailto:webkit-dev-boun...@lists.webkit.org] On Behalf Of Filip Pizlo
> Sent: Thursday, June 21, 2012 3:50 PM
> To: WebKit Development
> Subject: [webkit-dev] SH4, MIPS, and legacy-ARM assemblers in 
> JavaScriptCore
> 
> 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.cgi/webkit-dev
> 
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] build.webkit.org down?

[Mark Rowe]

On 2012-06-21, at 15:46, Lucas Forschler  wrote:

> I'd like to see a 'test' buildbot up and running that we could use as a 
> staging area for trying out new changes before deploying to the production 
> server.  We could copy 
> /OpenSource/Tools/BuildSlaveSupport/build.webkit.org-config to 
> /OpenSource/Tools/BuildSlaveSupport/test.webkit.org-config, and have a test 
> build master that updates and outputs logs somewhere readable (public_html?). 
>  Then, we could make sure any changes work on the test master before 
> committing them to production.

Having a test master seems like a good idea. Doing it by keeping a complete 
second copy of the configuration checked in to SVN seems less than ideal.

- Mark

> On Jun 21, 2012, at 1:15 PM, William Siegrist wrote:
> 
>> The server does not run the unittests, but it does normally run `buildbot 
>> checkconfig`. However, we had to temporarily bypass the checkconfig test 
>> during restart due to a bug in Buildbot:
>> 
>> http://trac.buildbot.net/ticket/2279
>> 
>> The best thing to do when working on the buildbot config is to have buildbot 
>> installed on your local machine so you can test the config before 
>> committing. That avoids the confusion of the reconfig not happening and 
>> people thinking the automatic reconfig is just broken.
>> 
>> -Bill
>> 
>> 
>> On Jun 21, 2012, at 12:28 PM, Osztrogonac Csaba  wrote:
>> 
>>> Hi,
>>> 
>>> In this case we could have avoided the breakage with running this unittest.
>>> Can we make the master somehow run this unittest before restarting itself?
>>> 
>>> br,
>>> Ossy
>>> 
>>> Eric Seidel írta:
 One can run:
 http://trac.webkit.org/browser/trunk/Tools/BuildSlaveSupport/build.webkit.org-config/mastercfg_unittest.py
 to test the master locally, but that's all I know of.
 On Thu, Jun 21, 2012 at 11:15 AM, Sergio Villar Senin
  wrote:
> En 21/06/12 19:54, William Siegrist escribiu:
>> On Jun 21, 2012, at 10:43 AM, Jon Lee  wrote:
>> 
>>> Is something being upgraded right now?
>>> 
>> No, the config file has a problem in it which is unrelated to our 
>> upgrade as far as I can tell. I'm trying to track down what happened.
>> 
>> $ buildbot checkconfig
> Do we have any tool that allows to check locally changes in the slaves
> configuration?
> 
> BR
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>> 
>>> ___
>>> webkit-dev mailing list
>>> webkit-dev@lists.webkit.org
>>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>> 
>> ___
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] SH4, MIPS, and legacy-ARM assemblers in JavaScriptCore

[Filip Pizlo]

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.cgi/webkit-dev

Re: [webkit-dev] build.webkit.org down?

[Lucas Forschler]

I'd like to see a 'test' buildbot up and running that we could use as a staging 
area for trying out new changes before deploying to the production server.  We 
could copy /OpenSource/Tools/BuildSlaveSupport/build.webkit.org-config to 
/OpenSource/Tools/BuildSlaveSupport/test.webkit.org-config, and have a test 
build master that updates and outputs logs somewhere readable (public_html?).  
Then, we could make sure any changes work on the test master before committing 
them to production.

Thoughts?
Lucas


On Jun 21, 2012, at 1:15 PM, William Siegrist wrote:

> The server does not run the unittests, but it does normally run `buildbot 
> checkconfig`. However, we had to temporarily bypass the checkconfig test 
> during restart due to a bug in Buildbot:
> 
> http://trac.buildbot.net/ticket/2279
> 
> The best thing to do when working on the buildbot config is to have buildbot 
> installed on your local machine so you can test the config before committing. 
> That avoids the confusion of the reconfig not happening and people thinking 
> the automatic reconfig is just broken.
> 
> -Bill
> 
> 
> On Jun 21, 2012, at 12:28 PM, Osztrogonac Csaba  wrote:
> 
>> Hi,
>> 
>> In this case we could have avoided the breakage with running this unittest.
>> Can we make the master somehow run this unittest before restarting itself?
>> 
>> br,
>> Ossy
>> 
>> Eric Seidel írta:
>>> One can run:
>>> http://trac.webkit.org/browser/trunk/Tools/BuildSlaveSupport/build.webkit.org-config/mastercfg_unittest.py
>>> to test the master locally, but that's all I know of.
>>> On Thu, Jun 21, 2012 at 11:15 AM, Sergio Villar Senin
>>>  wrote:
 En 21/06/12 19:54, William Siegrist escribiu:
> On Jun 21, 2012, at 10:43 AM, Jon Lee  wrote:
> 
>> Is something being upgraded right now?
>> 
> No, the config file has a problem in it which is unrelated to our upgrade 
> as far as I can tell. I'm trying to track down what happened.
> 
> $ buildbot checkconfig
 Do we have any tool that allows to check locally changes in the slaves
 configuration?
 
 BR
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>> ___
>>> webkit-dev mailing list
>>> webkit-dev@lists.webkit.org
>>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>> 
>> ___
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] Use dashboard region to support dragging frameless window in chromium extensions

[Jian Li]

Hi,

In Chromium port, we're working on supporting frameless windows for
extensions, that allow the web contents to have complete control of the
window. Frameless windows do not have the standard frame and the web
contents cover the whole window. Thus we need to provide a way to let the
web contents denote which part of the content area can be used to drag the
window. For example, the web contents draw the custom titlebar with the
icon, title, close button and etc. We want to let the user be able to drag
the titlebar in order to move the window around.

WebKit has already implemented the dashboard region support and exposed a
special CSS property -webkit-dashboard-region that lets you specify regions
for certain purpose, i.e. being excluded from dragging. The syntax of this
property is:
 -webkit-dashboard-region: dashboard-region(label geometry-type
offset-top offset-right offset-bottom offset-left)

Is it OK to reuse the dashboard region implementation to provide a way for
frameless windows to know about draggable regions? Can we introduce another
CSS property "-webkit-widget-region", that is essentially a synonym of
"-webkit-dashboard-region", since we do not want to get confused with
dashboard region support in Apple/WebKit. How do you think about this
approach?
 -webkit-widget-region: region(label geometry-type offset-top
offset-right offset-bottom offset-left)

Currently the existing dashboard region codes are wrapped inside the
feature guard ENABLE(DASHBOARD_SUPPORT). We're considering of putting this
new CSS property in a new feature guard, like ENABLE(WIDGET_REGION_SUPPORT)
such that "-webkit-dashboard-region" is only provided
under ENABLE(DASHBOARD_SUPPORT) as it is now and "-webkit-widget-region"
is only exposed under ENABLE(WIDGET_REGION_SUPPORT). How do you think?


Thanks,

Jian
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] build.webkit.org down?

[William Siegrist]

The server does not run the unittests, but it does normally run `buildbot 
checkconfig`. However, we had to temporarily bypass the checkconfig test during 
restart due to a bug in Buildbot:

http://trac.buildbot.net/ticket/2279

The best thing to do when working on the buildbot config is to have buildbot 
installed on your local machine so you can test the config before committing. 
That avoids the confusion of the reconfig not happening and people thinking the 
automatic reconfig is just broken.

-Bill


On Jun 21, 2012, at 12:28 PM, Osztrogonac Csaba  wrote:

> Hi,
> 
> In this case we could have avoided the breakage with running this unittest.
> Can we make the master somehow run this unittest before restarting itself?
> 
> br,
> Ossy
> 
> Eric Seidel írta:
>> One can run:
>> http://trac.webkit.org/browser/trunk/Tools/BuildSlaveSupport/build.webkit.org-config/mastercfg_unittest.py
>> to test the master locally, but that's all I know of.
>> On Thu, Jun 21, 2012 at 11:15 AM, Sergio Villar Senin
>>  wrote:
>>> En 21/06/12 19:54, William Siegrist escribiu:
 On Jun 21, 2012, at 10:43 AM, Jon Lee  wrote:
 
> Is something being upgraded right now?
> 
 No, the config file has a problem in it which is unrelated to our upgrade 
 as far as I can tell. I'm trying to track down what happened.
 
 $ buildbot checkconfig
>>> Do we have any tool that allows to check locally changes in the slaves
>>> configuration?
>>> 
>>> BR
>>> ___
>>> webkit-dev mailing list
>>> webkit-dev@lists.webkit.org
>>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>> ___
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] build.webkit.org down?

[Osztrogonac Csaba]

Hi,

In this case we could have avoided the breakage with running this unittest.
Can we make the master somehow run this unittest before restarting itself?

br,
Ossy

Eric Seidel írta:

One can run:
http://trac.webkit.org/browser/trunk/Tools/BuildSlaveSupport/build.webkit.org-config/mastercfg_unittest.py

to test the master locally, but that's all I know of.

On Thu, Jun 21, 2012 at 11:15 AM, Sergio Villar Senin
 wrote:

En 21/06/12 19:54, William Siegrist escribiu:

On Jun 21, 2012, at 10:43 AM, Jon Lee  wrote:


Is something being upgraded right now?


No, the config file has a problem in it which is unrelated to our upgrade as 
far as I can tell. I'm trying to track down what happened.

$ buildbot checkconfig

Do we have any tool that allows to check locally changes in the slaves
configuration?

BR
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] build.webkit.org down?

[Eric Seidel]

One can run:
http://trac.webkit.org/browser/trunk/Tools/BuildSlaveSupport/build.webkit.org-config/mastercfg_unittest.py

to test the master locally, but that's all I know of.

On Thu, Jun 21, 2012 at 11:15 AM, Sergio Villar Senin
 wrote:
> En 21/06/12 19:54, William Siegrist escribiu:
>> On Jun 21, 2012, at 10:43 AM, Jon Lee  wrote:
>>
>>> Is something being upgraded right now?
>>>
>>
>> No, the config file has a problem in it which is unrelated to our upgrade as 
>> far as I can tell. I'm trying to track down what happened.
>>
>> $ buildbot checkconfig
>
> Do we have any tool that allows to check locally changes in the slaves
> configuration?
>
> BR
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] build.webkit.org down?

[Sergio Villar Senin]

En 21/06/12 19:54, William Siegrist escribiu:
> On Jun 21, 2012, at 10:43 AM, Jon Lee  wrote:
> 
>> Is something being upgraded right now?
>>
> 
> No, the config file has a problem in it which is unrelated to our upgrade as 
> far as I can tell. I'm trying to track down what happened. 
> 
> $ buildbot checkconfig

Do we have any tool that allows to check locally changes in the slaves
configuration?

BR
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] build.webkit.org down?

[William Siegrist]

On Jun 21, 2012, at 10:54 AM, William Siegrist  wrote:

> On Jun 21, 2012, at 10:43 AM, Jon Lee  wrote:
> 
>> Is something being upgraded right now?
>> 
> 
> No, the config file has a problem in it which is unrelated to our upgrade as 
> far as I can tell. I'm trying to track down what happened. 
> 


Rev 120937 broke it. I updated the working copy to 120936 to get it back up for 
now. 

http://trac.webkit.org/changeset/120937


-Bill


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] build.webkit.org down?

[William Siegrist]

On Jun 21, 2012, at 10:43 AM, Jon Lee  wrote:

> Is something being upgraded right now?
> 

No, the config file has a problem in it which is unrelated to our upgrade as 
far as I can tell. I'm trying to track down what happened. 

$ buildbot checkconfig
Unhandled Error
Traceback (most recent call last):
  File "/opt/local/bin/buildbot", line 4, in 
runner.run()
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/buildbot/scripts/runner.py",
 line 1350, in run
if not doCheckConfig(so):
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/buildbot/scripts/runner.py",
 line 1071, in doCheckConfig
return cl.load(quiet=quiet)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/buildbot/scripts/checkconfig.py",
 line 29, in load
self.basedir, self.configFileName)
---  ---
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/buildbot/config.py",
 line 144, in loadConfig
exec f in localDict
  File "/Volumes/sas/buildbot/webkit/master.cfg", line 886, in 
loadBuilderConfig(c)
  File "/Volumes/sas/buildbot/webkit/master.cfg", line 864, in loadBuilderConfig
builder["factory"] = factory(*factoryArgs)
exceptions.TypeError: __init__() takes exactly 4 arguments (5 given)
Configuration Errors:
  error while parsing config file: __init__() takes exactly 4 arguments (5 
given) (traceback in logfile)


-Bill

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] Hardware Acceleration

[Darin Adler]

On Jun 21, 2012, at 2:49 AM, ketan goyal wrote:

> I am working on some 3D stuff and need hardware acceleration for performance.
> 
> So, I am wondering if Hardware Acceleration is supported for GTK port in 
> webkit ?

I think you may misunderstand the purpose of this mailing list.

This is the mailing list where someone should send messages if participating in 
the development of WebKit, say by contributing patches or testing and filing 
bugs. We discuss the development of WebKit here.

It’s not a place to ask about features you’d like to use in WebKit or help 
adapting WebKit for your work without contributing to the WebKit project.

I suggest asking on another list, perhaps webkit-help. This page explains 
.

-- Darin
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] Hardware Acceleration

[ketan goyal]

Hi,


I am working on some 3D stuff and need hardware acceleration for performance.

So, I am wondering if Hardware Acceleration is supported for GTK port
in webkit ?


-- 
Regards
Ketan Goyal
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev