<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I'm all for this but I don't know anything about markdown. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">What's the best way to proceed?<br><br>-Filip</div><div><br>On Jan 28, 2016, at 9:24 PM, Timothy Hatcher <<a href="mailto:timothy@apple.com">timothy@apple.com</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>They should be markdown files like we do for the code style and policy documents.</div><div><br></div><div><a href="https://trac.webkit.org/browser/trunk/Websites/webkit.org/code-style.md">https://trac.webkit.org/browser/trunk/Websites/webkit.org/code-style.md</a></div><div><br></div><div>We can then make Wordpress pages on the site that load the markdown.<br><br>Maybe put them in a /docs/b3/ directory?<br><br><div><div>— Timothy Hatcher</div></div></div><div><br>On Jan 28, 2016, at 4:48 PM, Filip Pizlo <<a href="mailto:fpizlo@apple.com">fpizlo@apple.com</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8">I guess we could put it in Websites/<a href="http://webkit.org/b3" class="">webkit.org/b3</a>. Then patches could edit both B3 and the documentation in one go, and the documentation would go live when it’s committed.<div class=""><br class=""></div><div class="">Does anyone object to this?</div><div class=""><br class=""></div><div class="">-Filip<br class=""><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 28, 2016, at 4:39 PM, Saam barati <<a href="mailto:sbarati@apple.com" class="">sbarati@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Yeah. That’d be the easiest way to keep it up IMO.<div class=""><br class=""></div><div class="">Saam</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jan 28, 2016, at 4:37 PM, Filip Pizło <<a href="mailto:fpizlo@apple.com" class="">fpizlo@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">+1</div><div class=""><br class=""></div><div class="">Do you think we should move the documentation to a file in svn so that it can be reviewed as part of patch review?<br class=""><br class="">-Filip</div><div class=""><br class="">On Jan 28, 2016, at 4:32 PM, Saam barati <<a href="mailto:sbarati@apple.com" class="">sbarati@apple.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class="">This is great. Thanks Fil.<div class=""><br class=""><div class="">I propose that we do all that we can to keep this updated.</div><div class="">I suggest that all patches that change to the IR should also include with it </div><div class="">a change to the documentation, and that reviewers should require this.</div><div class=""><br class=""></div><div class="">It’d also be great if other significant changes that seem like the deserve</div><div class="">a mention in the documentation also get added as part of patches.</div><div class=""><br class=""></div><div class="">Saam</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jan 28, 2016, at 4:23 PM, Filip Pizlo <<a href="mailto:fpizlo@apple.com" class="">fpizlo@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi everyone,<div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">If you’re interested in how it works, I’ve started writing documentation. I’ll be adding more to it soon!</div><div class=""><a href="https://trac.webkit.org/wiki/BareBonesBackend" class="">https://trac.webkit.org/wiki/BareBonesBackend</a></div><div class=""><a href="https://trac.webkit.org/wiki/B3IntermediateRepresentation" class="">https://trac.webkit.org/wiki/B3IntermediateRepresentation</a></div><div class=""><br class=""></div><div class="">-Filip</div><div class=""><br class=""></div></div>_______________________________________________<br class="">webkit-dev mailing list<br class=""><a href="mailto:webkit-dev@lists.webkit.org" class="">webkit-dev@lists.webkit.org</a><br class=""><a href="https://lists.webkit.org/mailman/listinfo/webkit-dev" class="">https://lists.webkit.org/mailman/listinfo/webkit-dev</a><br class=""></div></blockquote></div><br class=""></div></div></div></blockquote></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>webkit-dev mailing list</span><br><span><a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a></span><br><span><a href="https://lists.webkit.org/mailman/listinfo/webkit-dev">https://lists.webkit.org/mailman/listinfo/webkit-dev</a></span><br></div></blockquote></div></blockquote></body></html>