I plan to write more on this topic soon.
> 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
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,
I'm all for this but I don't know anything about markdown.
What's the best way to proceed?
> 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
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.
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
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:
For a refresher on the syntax.
Tim, could you create a page that loads the markdown file?
> On Jan
Markdown is pretty similar to the wiki formatting and very simple.
You can look at a cheatsheet if you login to the blog:
I have also used this HTML to Markdown converter before:
The pages are
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.
I also added:
> On Jan 29, 2016, at 10:05 AM, Filip Pizło wrote:
> Thank you! I'll convert them today.
> On Jan 29, 2016, at 10:02 AM, Timothy Hatcher
It is part of the HTML specification:
Chrome seems to support it. It is also covered by the W3C web-platform tests.
Thank you! I'll convert them today.
> 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:
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
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
On Sat, Jan 30, 2016 at 2:51 AM, Chris Dumez wrote:
> It is part of the HTML specification:
> 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”
I started coverting the documentation to Markdown. I don’t think this is a
- 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
Mail list logo