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

2016-01-29 Thread Filip Pizło
Context: https://trac.webkit.org/wiki/b3Discussion2015

I plan to write more on this topic soon. 

-Filip

> On Jan 28, 2016, at 11:12 PM, Stéphane Letz  wrote:
> 
> 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-29 Thread Michael Catanzaro
On Fri, 2016-01-29 at 13:44 +0900, Yusuke SUZUKI wrote:
> 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

https://bugs.webkit.org/show_bug.cgi?id=153647 looks pretty serious as
well.

Glad we're getting close though!

Michael
___
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-29 Thread Filip Pizło
I'm all for this but I don't know anything about markdown. 

What's the best way to proceed?

-Filip

> On Jan 28, 2016, at 9:24 PM, Timothy Hatcher  wrote:
> 
> 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


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

2016-01-29 Thread Konstantin Tokarev


29.01.2016, 03:23, "Filip Pizlo" :
> 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
>

Will it be feasible to port FTL/B3 to 32-bit platforms?
Thanks!

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


Re: [webkit-dev] Thought about Nix JavaScriptCore port

2016-01-29 Thread Konstantin Tokarev


01.01.2016, 04:26, "Michael Catanzaro" :
> On Thu, 2015-12-31 at 19:25 +0300, Konstantin Tokarev wrote:
>>  Hi Yusuke,
>>
>>  What is the status of this proposal?
>>  AFAICS there were no serious objections, quite the opposite, many
>>  people support your proposal (me too). However, no patches were
>>  landed yet.
>
> I only wonder why it is called Nix? Is it named for http://nixos.org/?
> Or is just supposed to be a generic *nix Unix? Maybe a better name for
> the port would simply be "jsc" or "js"...? It's just when I see "Nix" I
> don't think "JSC only."

I agree, and this port can easily support Windows, invalidating "Nix" name.
However, if we call this port "JSC", build-jsc --jsc will look strange, and
build-webkit --jsc might be misunderstood as "build only JSC part of this
port", i.e. as synonym of build-jsc.

Does anyone have an idea how to name this port?


>
> Did you test this with build-jsc? I guess it's fine to make 'build-
> webkit --nix' do the right thing, but I bet it'd be more convenient to
> just use the build-jsc command.
>
> Michael
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev

-- 
Regards,
Konstantin
___
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-29 Thread saam barati
I'm happy to convert the document to markdown. Can you send me your latest 
revision or post it to the website?

I usually look at:
http://daringfireball.net/projects/markdown/syntax
For a refresher on the syntax.

Tim, could you create a page that loads the markdown file?

Thanks,
Saam

> On Jan 29, 2016, at 12:06 AM, Filip Pizło  wrote:
> 
> I'm all for this but I don't know anything about markdown. 
> 
> What's the best way to proceed?
> 
> -Filip
> 
>> On Jan 28, 2016, at 9:24 PM, Timothy Hatcher  wrote:
>> 
>> 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
___
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-29 Thread Timothy Hatcher
Markdown is pretty similar to the wiki formatting and very simple.

You can look at a cheatsheet if you login to the blog: 
https://webkit.org/wp/wp-admin/post.php?post=4300=edit

I have also used this HTML to Markdown converter before: 
http://domchristie.github.io/to-markdown/

The pages are created:

https://webkit.org/documentation/b3/ loads /docs/b3/bare-bones-backend.md
https://webkit.org/documentation/b3/intermediate-representation/ loads 
/docs/b3/intermediate-representation.md

Once those files are added to SVN, they will get picked up by the site. I can 
change those to point to other names if you want something different.

— Timothy Hatcher

> On Jan 29, 2016, at 9:34 AM, saam barati  wrote:
> 
> I'm happy to convert the document to markdown. Can you send me your latest 
> revision or post it to the website?
> 
> I usually look at:
> http://daringfireball.net/projects/markdown/syntax 
> 
> For a refresher on the syntax.
> 
> Tim, could you create a page that loads the markdown file?
> 
> Thanks,
> Saam
> 
> On Jan 29, 2016, at 12:06 AM, Filip Pizło  > wrote:
> 
>> I'm all for this but I don't know anything about markdown. 
>> 
>> What's the best way to proceed?
>> 
>> -Filip
>> 
>> On Jan 28, 2016, at 9:24 PM, Timothy Hatcher > > wrote:
>> 
>>> 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 
>> 

Re: [webkit-dev] Removing ENABLE(DATA_TRANSFER_ITEMS)

2016-01-29 Thread Anders Carlsson
While we do understand the value for your port in keeping these classes, WebKit 
has never had any obligations to downstream ports and forks. Nothing is 
stopping you from copying these files to your repository.

Gyuyoung, since nobody else has objected I think it’s fine to remove this.

- Anders


> On Jan 26, 2016, at 2:04 AM, Konstantin Tokarev  wrote:
> 
> 
> 
> 22.12.2015, 09:02, "Gyuyoung Kim" :
>> Hello,
>> 
>> It looks like no ports have used a data transfer items feature. Even the 
>> feature hasn't been updated since 2011. If anyone doesn't have a plan to use 
>> it in future, I plan to remove it. Any objections ?
> 
> In Qt port (I'm working on it downstream) we have implementations of 
> DataTransferItem and DataTransferItemList, please don't remove them.
> 
> 
> -- 
> Regards,
> Konstantin
> ___
> 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-29 Thread Timothy Hatcher
I also added:

https://webkit.org/documentation/b3/air/ loads 
/docs/b3/assembly-intermediate-representation.md

> On Jan 29, 2016, at 10:05 AM, Filip Pizło  wrote:
> 
> Thank you!  I'll convert them today. 
> 
> -Filip
> 
> On Jan 29, 2016, at 10:02 AM, Timothy Hatcher  > wrote:
> 
>> Markdown is pretty similar to the wiki formatting and very simple.
>> 
>> You can look at a cheatsheet if you login to the blog: 
>> https://webkit.org/wp/wp-admin/post.php?post=4300=edit 
>> 
>> 
>> I have also used this HTML to Markdown converter before: 
>> http://domchristie.github.io/to-markdown/ 
>> 
>> 
>> The pages are created:
>> 
>> https://webkit.org/documentation/b3/  
>> loads /docs/b3/bare-bones-backend.md
>> https://webkit.org/documentation/b3/intermediate-representation/ 
>>  loads 
>> /docs/b3/intermediate-representation.md
>> 
>> Once those files are added to SVN, they will get picked up by the site. I 
>> can change those to point to other names if you want something different.
>> 
>> — Timothy Hatcher
>> 
>>> On Jan 29, 2016, at 9:34 AM, saam barati >> > wrote:
>>> 
>>> I'm happy to convert the document to markdown. Can you send me your latest 
>>> revision or post it to the website?
>>> 
>>> I usually look at:
>>> http://daringfireball.net/projects/markdown/syntax 
>>> 
>>> For a refresher on the syntax.
>>> 
>>> Tim, could you create a page that loads the markdown file?
>>> 
>>> Thanks,
>>> Saam
>>> 
>>> On Jan 29, 2016, at 12:06 AM, Filip Pizło >> > wrote:
>>> 
 I'm all for this but I don't know anything about markdown. 
 
 What's the best way to proceed?
 
 -Filip
 
 On Jan 28, 2016, at 9:24 PM, Timothy Hatcher > wrote:
 
> 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 
>> 

Re: [webkit-dev] Removing ENABLE(DATA_TRANSFER_ITEMS)

2016-01-29 Thread Chris Dumez
Hi,

It is part of the HTML specification:
https://html.spec.whatwg.org/multipage/interaction.html#the-datatransferitemlist-interface
https://html.spec.whatwg.org/multipage/interaction.html#datatransferitem

Chrome seems to support it. It is also covered by the W3C web-platform tests.
Should we work on enabling this feature rather than removing it?

Kr,
--
 Chris Dumez




> On Dec 21, 2015, at 10:02 PM, Gyuyoung Kim  wrote:
> 
> Hello,
> 
> It looks like no ports have used a data transfer items feature. Even the 
> feature hasn't been updated since 2011. If anyone doesn't have a plan to use 
> it in future, I plan to remove it. Any objections ?
> 
> Gyuyoung. 
> ___
> 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-29 Thread Filip Pizło
Thank you!  I'll convert them today. 

-Filip

> On Jan 29, 2016, at 10:02 AM, Timothy Hatcher  wrote:
> 
> Markdown is pretty similar to the wiki formatting and very simple.
> 
> You can look at a cheatsheet if you login to the blog: 
> https://webkit.org/wp/wp-admin/post.php?post=4300=edit
> 
> I have also used this HTML to Markdown converter before: 
> http://domchristie.github.io/to-markdown/
> 
> The pages are created:
> 
> https://webkit.org/documentation/b3/ loads /docs/b3/bare-bones-backend.md
> https://webkit.org/documentation/b3/intermediate-representation/ loads 
> /docs/b3/intermediate-representation.md
> 
> Once those files are added to SVN, they will get picked up by the site. I can 
> change those to point to other names if you want something different.
> 
> — Timothy Hatcher
> 
>> On Jan 29, 2016, at 9:34 AM, saam barati  wrote:
>> 
>> I'm happy to convert the document to markdown. Can you send me your latest 
>> revision or post it to the website?
>> 
>> I usually look at:
>> http://daringfireball.net/projects/markdown/syntax
>> For a refresher on the syntax.
>> 
>> Tim, could you create a page that loads the markdown file?
>> 
>> Thanks,
>> Saam
>> 
>>> On Jan 29, 2016, at 12:06 AM, Filip Pizło  wrote:
>>> 
>>> I'm all for this but I don't know anything about markdown. 
>>> 
>>> What's the best way to proceed?
>>> 
>>> -Filip
>>> 
 On Jan 28, 2016, at 9:24 PM, Timothy Hatcher  wrote:
 
 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
> 
___
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-29 Thread Filip Pizlo
Follow up on this:

> On Jan 29, 2016, at 11:38 AM, Filip Pizlo  wrote:
> 
> I started coverting the documentation to Markdown.  I don’t think this is a 
> good idea.
> 
> - Markdown has no definition lists.  The entire IR document is a definition 
> list.  I don’t want B3’s documentation to be blocked on this issue.

It turns out that it does have them, but they are very weak.  For example, you 
can’t have code blocks or paragraphs inside them.  We want to have code blocks 
inside opcode definitions, to show examples.

> - Markdown’s conversion step makes the workflow awkward.  I’m not going to 
> use some Markdown editing app - that will prevent me from being able to 
> properly format code examples.  I need a code editor for that.

This was hard to get around.  This isn’t a problem with Markdown, but rather, a 
problem with using Wordpress to render Markdown that is in svn.  There is no 
way to preview the Markdown before committing it.  That would lead to unusual 
problems, where after a patch is landed, the patch author or someone else would 
have to do a bunch of blind follow-up commits to fix any style issues, like 
code blocks that don’t fit properly or whatever.

Considering that we will have to be hacking raw HTML inside those Markdown 
files (due to definition lists), the lack of preview basically means that you 
have no way of predicting what the your HTML will render like.

> 
> I think that this documentation should be HTML.  I don’t think we should 
> expend a lot of energy to formatting it nicely.  The point of this document 
> is for it to be read by engineers while they hack code.

I landed raw HTML documentation: http://trac.webkit.org/changeset/195841 


I filed this bug about improving its style: 
https://bugs.webkit.org/show_bug.cgi?id=153674 


-Filip


> 
> -Filip
> 
> 
>> On Jan 29, 2016, at 10:12 AM, Timothy Hatcher > > wrote:
>> 
>> I also added:
>> 
>> https://webkit.org/documentation/b3/air/ 
>>  loads 
>> /docs/b3/assembly-intermediate-representation.md
>> 
>>> On Jan 29, 2016, at 10:05 AM, Filip Pizło >> > wrote:
>>> 
>>> Thank you!  I'll convert them today. 
>>> 
>>> -Filip
>>> 
>>> On Jan 29, 2016, at 10:02 AM, Timothy Hatcher >> > wrote:
>>> 
 Markdown is pretty similar to the wiki formatting and very simple.
 
 You can look at a cheatsheet if you login to the blog: 
 https://webkit.org/wp/wp-admin/post.php?post=4300=edit 
 
 
 I have also used this HTML to Markdown converter before: 
 http://domchristie.github.io/to-markdown/ 
 
 
 The pages are created:
 
 https://webkit.org/documentation/b3/ 
  loads /docs/b3/bare-bones-backend.md
 https://webkit.org/documentation/b3/intermediate-representation/ 
  loads 
 /docs/b3/intermediate-representation.md
 
 Once those files are added to SVN, they will get picked up by the site. I 
 can change those to point to other names if you want something different.
 
 — Timothy Hatcher
 
> On Jan 29, 2016, at 9:34 AM, saam barati  > wrote:
> 
> I'm happy to convert the document to markdown. Can you send me your 
> latest revision or post it to the website?
> 
> I usually look at:
> http://daringfireball.net/projects/markdown/syntax 
> 
> For a refresher on the syntax.
> 
> Tim, could you create a page that loads the markdown file?
> 
> Thanks,
> Saam
> 
> On Jan 29, 2016, at 12:06 AM, Filip Pizło  > wrote:
> 
>> I'm all for this but I don't know anything about markdown. 
>> 
>> What's the best way to proceed?
>> 
>> -Filip
>> 
>> On Jan 28, 2016, at 9:24 PM, Timothy Hatcher > > wrote:
>> 
>>> 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:
>>> 

Re: [webkit-dev] Removing ENABLE(DATA_TRANSFER_ITEMS)

2016-01-29 Thread Gyuyoung Kim
Chris and Alexey seem to want to keep the feature because it is part of w3c
spec. I don't want to remove it if someone has any plan to use|enable it in
future.

Gyuyoung.

On Sat, Jan 30, 2016 at 2:51 AM, Chris Dumez  wrote:

> Hi,
>
> It is part of the HTML specification:
>
> https://html.spec.whatwg.org/multipage/interaction.html#the-datatransferitemlist-interface
> https://html.spec.whatwg.org/multipage/interaction.html#datatransferitem
>
> Chrome seems to support it. It is also covered by the W3C web-platform
> tests.
> Should we work on enabling this feature rather than removing it?
>
> Kr,
> --
>  Chris Dumez
>
>
>
>
> On Dec 21, 2015, at 10:02 PM, Gyuyoung Kim 
> wrote:
>
> Hello,
>
> It looks like no ports have used a data transfer items feature. Even the
> feature hasn't been updated since 2011. If anyone doesn't have a plan to
> use it in future, I plan to remove it. Any objections ?
>
> Gyuyoung.
> ___
> 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] Intent to implement in Blink: CSS properties break-{after, before, inside}

2016-01-29 Thread David Hyatt
https://bugs.webkit.org/attachment.cgi?id=270221=review

> On Jan 21, 2016, at 8:35 AM, Morten Stenshorne  wrote:
> 
> Thanks for your quick response!
> 
> David Hyatt  writes:
> 
>> We are in favor of those properties. If you want to talk about “avoid”
>> specifically offline, I outlined a plan for implementing that property
>> in one of the webkit bugs (I’ll have to hunt down the link). I think
>> it basically needs to work a bit like margin collapsing in the sense
>> that you need to propagate out knowledge of the break intent at the
>> top and bottom of blocks, and then “collapse” with adjacent blocks to
>> determine what the break intent should be at a given position.
>> 
>> dave
>> 
>>> On Jan 19, 2016, at 1:12 PM, Morten Stenshorne  wrote:
>>> 
>>> Hello WebKit! :)
>>> 
>>> I'm planning to implement the CSS properties break-after, break-before
>>> and break-inside [1] in Blink. As part of that process, I need to ask
>>> other browser vendors about their views / plans regarding this web
>>> platform feature. I'd especially like to know if you have anything
>>> against implementing these properties (apart from priorities).
>>> 
>>> Thanks in advance!
>>> 
>>> [1] https://www.chromestatus.com/feature/5630943616303104
>>> 
>>> -- 
>>>  Morten Stenshorne, developer, Opera Software ASA 
>>> -- http://www.opera.com/ -
>>> ___
>>> webkit-dev mailing list
>>> webkit-dev@lists.webkit.org
>>> https://lists.webkit.org/mailman/listinfo/webkit-dev
>> 
>> 
> 
> -- 
>  Morten Stenshorne, developer, Opera Software ASA 
> -- http://www.opera.com/ -

___
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-29 Thread Filip Pizlo
I started coverting the documentation to Markdown.  I don’t think this is a 
good idea.

- Markdown has no definition lists.  The entire IR document is a definition 
list.  I don’t want B3’s documentation to be blocked on this issue.
- Markdown’s conversion step makes the workflow awkward.  I’m not going to use 
some Markdown editing app - that will prevent me from being able to properly 
format code examples.  I need a code editor for that.

I think that this documentation should be HTML.  I don’t think we should expend 
a lot of energy to formatting it nicely.  The point of this document is for it 
to be read by engineers while they hack code.

-Filip


> On Jan 29, 2016, at 10:12 AM, Timothy Hatcher  wrote:
> 
> I also added:
> 
> https://webkit.org/documentation/b3/air/ 
>  loads 
> /docs/b3/assembly-intermediate-representation.md
> 
>> On Jan 29, 2016, at 10:05 AM, Filip Pizło > > wrote:
>> 
>> Thank you!  I'll convert them today. 
>> 
>> -Filip
>> 
>> On Jan 29, 2016, at 10:02 AM, Timothy Hatcher > > wrote:
>> 
>>> Markdown is pretty similar to the wiki formatting and very simple.
>>> 
>>> You can look at a cheatsheet if you login to the blog: 
>>> https://webkit.org/wp/wp-admin/post.php?post=4300=edit 
>>> 
>>> 
>>> I have also used this HTML to Markdown converter before: 
>>> http://domchristie.github.io/to-markdown/ 
>>> 
>>> 
>>> The pages are created:
>>> 
>>> https://webkit.org/documentation/b3/  
>>> loads /docs/b3/bare-bones-backend.md
>>> https://webkit.org/documentation/b3/intermediate-representation/ 
>>>  loads 
>>> /docs/b3/intermediate-representation.md
>>> 
>>> Once those files are added to SVN, they will get picked up by the site. I 
>>> can change those to point to other names if you want something different.
>>> 
>>> — Timothy Hatcher
>>> 
 On Jan 29, 2016, at 9:34 AM, saam barati > wrote:
 
 I'm happy to convert the document to markdown. Can you send me your latest 
 revision or post it to the website?
 
 I usually look at:
 http://daringfireball.net/projects/markdown/syntax 
 
 For a refresher on the syntax.
 
 Tim, could you create a page that loads the markdown file?
 
 Thanks,
 Saam
 
 On Jan 29, 2016, at 12:06 AM, Filip Pizło > wrote:
 
> I'm all for this but I don't know anything about markdown. 
> 
> What's the best way to proceed?
> 
> -Filip
> 
> On Jan 28, 2016, at 9:24 PM, Timothy Hatcher  > wrote:
> 
>> 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