Re: [webkit-dev] Some text about the B3 compiler

2016-01-28 Thread Stéphane Letz 
Maybe a stupid question, but what is a the rationale for this new backend? (I 
was thinking LLVM JIT was used instead to produce machine code….)

Thanks.

Stéphane Letz

Le 29 janv. 2016 à 01:23, Filip Pizlo  a écrit :

> Hi everyone,
> 
> We’ve been working on a new compiler backend for the FTL JIT, which we call 
> B3.  It stands for “Bare Bones Backend”.  We recently enabled it on X86/Mac, 
> and we’re working hard to enable it on other platforms.
> 
> If you’re interested in how it works, I’ve started writing documentation.  
> I’ll be adding more to it soon!
> https://trac.webkit.org/wiki/BareBonesBackend
> https://trac.webkit.org/wiki/B3IntermediateRepresentation
> 
> -Filip
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev

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

Re: [webkit-dev] Some text about the B3 compiler

2016-01-28 Thread Saam barati 
Yeah. That’d be the easiest way to keep it up IMO.

Saam

> On Jan 28, 2016, at 4:37 PM, Filip Pizło  wrote:
> 
> +1
> 
> Do you think we should move the documentation to a file in svn so that it can 
> be reviewed as part of patch review?
> 
> -Filip
> 
> On Jan 28, 2016, at 4:32 PM, Saam barati  > wrote:
> 
>> This is great. Thanks Fil.
>> 
>> I propose that we do all that we can to keep this updated.
>> I suggest that all patches that change to the IR should also include with it 
>> a change to the documentation, and that reviewers should require this.
>> 
>> It’d also be great if other significant changes that seem like the deserve
>> a mention in the documentation also get added as part of patches.
>> 
>> Saam
>> 
>>> On Jan 28, 2016, at 4:23 PM, Filip Pizlo >> > wrote:
>>> 
>>> Hi everyone,
>>> 
>>> We’ve been working on a new compiler backend for the FTL JIT, which we call 
>>> B3.  It stands for “Bare Bones Backend”.  We recently enabled it on 
>>> X86/Mac, and we’re working hard to enable it on other platforms.
>>> 
>>> If you’re interested in how it works, I’ve started writing documentation.  
>>> I’ll be adding more to it soon!
>>> https://trac.webkit.org/wiki/BareBonesBackend 
>>> 
>>> https://trac.webkit.org/wiki/B3IntermediateRepresentation 
>>> 
>>> 
>>> -Filip
>>> 
>>> ___
>>> webkit-dev mailing list
>>> webkit-dev@lists.webkit.org 
>>> https://lists.webkit.org/mailman/listinfo/webkit-dev 
>>> 
>> 

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

Re: [webkit-dev] Some text about the B3 compiler

2016-01-28 Thread Filip Pizlo 
I guess we could put it in Websites/webkit.org/b3 .  Then 
patches could edit both B3 and the documentation in one go, and the 
documentation would go live when it’s committed.

Does anyone object to this?

-Filip


> On Jan 28, 2016, at 4:39 PM, Saam barati  wrote:
> 
> Yeah. That’d be the easiest way to keep it up IMO.
> 
> Saam
> 
>> On Jan 28, 2016, at 4:37 PM, Filip Pizło > > wrote:
>> 
>> +1
>> 
>> Do you think we should move the documentation to a file in svn so that it 
>> can be reviewed as part of patch review?
>> 
>> -Filip
>> 
>> On Jan 28, 2016, at 4:32 PM, Saam barati > > wrote:
>> 
>>> This is great. Thanks Fil.
>>> 
>>> I propose that we do all that we can to keep this updated.
>>> I suggest that all patches that change to the IR should also include with 
>>> it 
>>> a change to the documentation, and that reviewers should require this.
>>> 
>>> It’d also be great if other significant changes that seem like the deserve
>>> a mention in the documentation also get added as part of patches.
>>> 
>>> Saam
>>> 
 On Jan 28, 2016, at 4:23 PM, Filip Pizlo > wrote:
 
 Hi everyone,
 
 We’ve been working on a new compiler backend for the FTL JIT, which we 
 call B3.  It stands for “Bare Bones Backend”.  We recently enabled it on 
 X86/Mac, and we’re working hard to enable it on other platforms.
 
 If you’re interested in how it works, I’ve started writing documentation.  
 I’ll be adding more to it soon!
 https://trac.webkit.org/wiki/BareBonesBackend 
 
 https://trac.webkit.org/wiki/B3IntermediateRepresentation 
 
 
 -Filip
 
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org 
 https://lists.webkit.org/mailman/listinfo/webkit-dev 
 
>>> 
> 

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

Re: [webkit-dev] Some text about the B3 compiler

2016-01-28 Thread Saam barati 
This is great. Thanks Fil.

I propose that we do all that we can to keep this updated.
I suggest that all patches that change to the IR should also include with it 
a change to the documentation, and that reviewers should require this.

It’d also be great if other significant changes that seem like the deserve
a mention in the documentation also get added as part of patches.

Saam

> On Jan 28, 2016, at 4:23 PM, Filip Pizlo  wrote:
> 
> Hi everyone,
> 
> We’ve been working on a new compiler backend for the FTL JIT, which we call 
> B3.  It stands for “Bare Bones Backend”.  We recently enabled it on X86/Mac, 
> and we’re working hard to enable it on other platforms.
> 
> If you’re interested in how it works, I’ve started writing documentation.  
> I’ll be adding more to it soon!
> https://trac.webkit.org/wiki/BareBonesBackend 
> 
> https://trac.webkit.org/wiki/B3IntermediateRepresentation 
> 
> 
> -Filip
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev

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

Re: [webkit-dev] Some text about the B3 compiler

2016-01-28 Thread Filip Pizło 
+1

Do you think we should move the documentation to a file in svn so that it can 
be reviewed as part of patch review?

-Filip

> On Jan 28, 2016, at 4:32 PM, Saam barati  wrote:
> 
> This is great. Thanks Fil.
> 
> I propose that we do all that we can to keep this updated.
> I suggest that all patches that change to the IR should also include with it 
> a change to the documentation, and that reviewers should require this.
> 
> It’d also be great if other significant changes that seem like the deserve
> a mention in the documentation also get added as part of patches.
> 
> Saam
> 
>> On Jan 28, 2016, at 4:23 PM, Filip Pizlo  wrote:
>> 
>> Hi everyone,
>> 
>> We’ve been working on a new compiler backend for the FTL JIT, which we call 
>> B3.  It stands for “Bare Bones Backend”.  We recently enabled it on X86/Mac, 
>> and we’re working hard to enable it on other platforms.
>> 
>> If you’re interested in how it works, I’ve started writing documentation.  
>> I’ll be adding more to it soon!
>> https://trac.webkit.org/wiki/BareBonesBackend
>> https://trac.webkit.org/wiki/B3IntermediateRepresentation
>> 
>> -Filip
>> 
>> ___
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> https://lists.webkit.org/mailman/listinfo/webkit-dev
> 
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Some text about the B3 compiler

2016-01-28 Thread Andy Estes 
I was just going to suggest something similar! 

Andy

> On Jan 28, 2016, at 4:48 PM, Filip Pizlo  wrote:
> 
> I guess we could put it in Websites/webkit.org/b3 .  
> Then patches could edit both B3 and the documentation in one go, and the 
> documentation would go live when it’s committed.
> 
> Does anyone object to this?
> 
> -Filip
> 
> 
>> On Jan 28, 2016, at 4:39 PM, Saam barati > > wrote:
>> 
>> Yeah. That’d be the easiest way to keep it up IMO.
>> 
>> Saam
>> 
>>> On Jan 28, 2016, at 4:37 PM, Filip Pizło >> > wrote:
>>> 
>>> +1
>>> 
>>> Do you think we should move the documentation to a file in svn so that it 
>>> can be reviewed as part of patch review?
>>> 
>>> -Filip
>>> 
>>> On Jan 28, 2016, at 4:32 PM, Saam barati >> > wrote:
>>> 
 This is great. Thanks Fil.
 
 I propose that we do all that we can to keep this updated.
 I suggest that all patches that change to the IR should also include with 
 it 
 a change to the documentation, and that reviewers should require this.
 
 It’d also be great if other significant changes that seem like the deserve
 a mention in the documentation also get added as part of patches.
 
 Saam
 
> On Jan 28, 2016, at 4:23 PM, Filip Pizlo  > wrote:
> 
> Hi everyone,
> 
> We’ve been working on a new compiler backend for the FTL JIT, which we 
> call B3.  It stands for “Bare Bones Backend”.  We recently enabled it on 
> X86/Mac, and we’re working hard to enable it on other platforms.
> 
> If you’re interested in how it works, I’ve started writing documentation. 
>  I’ll be adding more to it soon!
> https://trac.webkit.org/wiki/BareBonesBackend 
> 
> https://trac.webkit.org/wiki/B3IntermediateRepresentation 
> 
> 
> -Filip
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org 
> https://lists.webkit.org/mailman/listinfo/webkit-dev 
> 
 
>> 
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev

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

[webkit-dev] A recent change to how WebKit XPC services work for development

2016-01-28 Thread Dan Bernstein 
The recent r195795  
changed how WebKit XPC services work for development.

I expect this change to not have any impact on most of your workflows, but read 
on for the details, and be on the lookout for any things that might have broken 
anyway.

The most noticeable effect of this change is that XPC services will no longer 
inherit all of the UI process’s environment variables automatically. To set an 
environment variable EXAMPLE to VALUE in the XPC services, you’ll need to set 
__XPC_EXAMPLE to VALUE in the UI process’s environment. In cases where our 
tools need to control the XPC services’ environment, the tools have been 
updated to do use the __XPC_ prefix. And setting __XPC_DYLD_FRAMEWORK_PATH or 
__XPC_DYLD_LIBRARY_PATH for the services isn’t necessary, since they know to 
look for frameworks and libraries relative to where they are.

Engineering builds will no longer contain both a normal variant and a 
.Development variant of each of the WebKit XPC services. Instead, they will 
contain only a normal variant of each service. However, the service name and 
bundle identifier will continue to have the .Development suffix.___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Some text about the B3 compiler

2016-01-28 Thread Yusuke SUZUKI 
Awesome, awesome work!
Thanks Fil and all the JSC B3 developers!

After this https://bugs.webkit.org/show_bug.cgi?id=153422 is landed,
jsc-layout-tests.yaml/js/script-tests/array-enumerators-functions.js.layout-ftl-eager-no-cjit
 is only the test failing in B3 on Linux GTK port! B3 in the other
platforms looks approaching :D

Regards,
Yusuke Suzuki

On Fri, Jan 29, 2016 at 9:49 AM, Andy Estes  wrote:

> I was just going to suggest something similar! 
>
> Andy
>
> On Jan 28, 2016, at 4:48 PM, Filip Pizlo  wrote:
>
> I guess we could put it in Websites/webkit.org/b3.  Then patches could
> edit both B3 and the documentation in one go, and the documentation would
> go live when it’s committed.
>
> Does anyone object to this?
>
> -Filip
>
>
> On Jan 28, 2016, at 4:39 PM, Saam barati  wrote:
>
> Yeah. That’d be the easiest way to keep it up IMO.
>
> Saam
>
> On Jan 28, 2016, at 4:37 PM, Filip Pizło  wrote:
>
> +1
>
> Do you think we should move the documentation to a file in svn so that it
> can be reviewed as part of patch review?
>
> -Filip
>
> On Jan 28, 2016, at 4:32 PM, Saam barati  wrote:
>
> This is great. Thanks Fil.
>
> I propose that we do all that we can to keep this updated.
> I suggest that all patches that change to the IR should also include with
> it
> a change to the documentation, and that reviewers should require this.
>
> It’d also be great if other significant changes that seem like the deserve
> a mention in the documentation also get added as part of patches.
>
> Saam
>
> On Jan 28, 2016, at 4:23 PM, Filip Pizlo  wrote:
>
> Hi everyone,
>
> We’ve been working on a new compiler backend for the FTL JIT, which we
> call B3.  It stands for “Bare Bones Backend”.  We recently enabled it on
> X86/Mac, and we’re working hard to enable it on other platforms.
>
> If you’re interested in how it works, I’ve started writing documentation.
> I’ll be adding more to it soon!
> https://trac.webkit.org/wiki/BareBonesBackend
> https://trac.webkit.org/wiki/B3IntermediateRepresentation
>
> -Filip
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
>
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Some text about the B3 compiler

2016-01-28 Thread Timothy Hatcher 
They should be markdown files like we do for the code style and policy 
documents.

https://trac.webkit.org/browser/trunk/Websites/webkit.org/code-style.md

We can then make Wordpress pages on the site that load the markdown.

Maybe put them in a /docs/b3/ directory?

— Timothy Hatcher

> On Jan 28, 2016, at 4:48 PM, Filip Pizlo  wrote:
> 
> I guess we could put it in Websites/webkit.org/b3.  Then patches could edit 
> both B3 and the documentation in one go, and the documentation would go live 
> when it’s committed.
> 
> Does anyone object to this?
> 
> -Filip
> 
> 
>> On Jan 28, 2016, at 4:39 PM, Saam barati  wrote:
>> 
>> Yeah. That’d be the easiest way to keep it up IMO.
>> 
>> Saam
>> 
>>> On Jan 28, 2016, at 4:37 PM, Filip Pizło  wrote:
>>> 
>>> +1
>>> 
>>> Do you think we should move the documentation to a file in svn so that it 
>>> can be reviewed as part of patch review?
>>> 
>>> -Filip
>>> 
 On Jan 28, 2016, at 4:32 PM, Saam barati  wrote:
 
 This is great. Thanks Fil.
 
 I propose that we do all that we can to keep this updated.
 I suggest that all patches that change to the IR should also include with 
 it 
 a change to the documentation, and that reviewers should require this.
 
 It’d also be great if other significant changes that seem like the deserve
 a mention in the documentation also get added as part of patches.
 
 Saam
 
> On Jan 28, 2016, at 4:23 PM, Filip Pizlo  wrote:
> 
> Hi everyone,
> 
> We’ve been working on a new compiler backend for the FTL JIT, which we 
> call B3.  It stands for “Bare Bones Backend”.  We recently enabled it on 
> X86/Mac, and we’re working hard to enable it on other platforms.
> 
> If you’re interested in how it works, I’ve started writing documentation. 
>  I’ll be adding more to it soon!
> https://trac.webkit.org/wiki/BareBonesBackend
> https://trac.webkit.org/wiki/B3IntermediateRepresentation
> 
> -Filip
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev