<div dir="ltr">On Wed, May 9, 2018 at 6:46 AM Michael Saboff <<a href="mailto:msaboff@apple.com">msaboff@apple.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="word-wrap:break-word;line-break:after-white-space"><div style="word-wrap:break-word;line-break:after-white-space">Yusuke,<div><br></div><div>What are the deficiencies you see in the current ARMv7 disassembler?</div></div></div></div></div></blockquote><div><br></div><div>This is just removing some code in WebKit tree. Basically there is no functionality difference.<br></div><div>Currently, MIPS and ARM use capstone disassembler. If we can use this for ARMv7, it simplifies the implementation.<br><br></div><div>I don't want to use capstone for X86, X86_64, and ARM64 right now since these instruction sets are really changing: new instructions are added frequently.<br></div><div>So I would like to have our own ones in the tree. But for MIPS, ARM and ARMv7, instruction sets are not so changed in terms of our JIT.<br><br></div><div>Best regards,<br></div><div>Yusuke Suzuki<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="word-wrap:break-word;line-break:after-white-space"><div style="word-wrap:break-word;line-break:after-white-space"><div><br></div><div>- Michael<br><div><br><blockquote type="cite"><div>On May 4, 2018, at 7:45 PM, Yusuke SUZUKI <<a href="mailto:utatane.tea@gmail.com" target="_blank">utatane.tea@gmail.com</a>> wrote:</div><br class="m_-7440217863479158993Apple-interchange-newline"><div><div dir="ltr">On Sat, May 5, 2018 at 11:27 AM Filip Pizlo <<a href="mailto:fpizlo@apple.com" target="_blank">fpizlo@apple.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We aren’t maintaining armv7. <br></blockquote><div><br></div><div>OK, thanks. I'll replace ARMv7 disassembler with capstone based one once capstone is adopted :)<br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
-Filip<br>
<br>
> On May 4, 2018, at 7:01 PM, Yusuke SUZUKI <<a href="mailto:utatane.tea@gmail.com" target="_blank">utatane.tea@gmail.com</a>> wrote:<br>
> <br>
> Hi WebKittens,<br>
> <br>
> JSC has X86, X86_64, ARM64, ARM, ARMv7, and MIPS JIT architectures.<br>
> While X86, X86_64, and ARM64 is maintained by build bots configured by Apple,<br>
> the other architectures are maintained by the community.<br>
> <br>
> Recently, I'm about to adopting capstone disassembler for MIPS and ARM.<br>
> And I'm also wondering if ARMv7 can use it instead of our own disassembler.<br>
> <br>
> So my question is, is ARMv7 JIT maintained by Apple right now? Or is it maintained by the community?<br>
> If Apple does not maintain it right now, I would like to drop ARMv7 disassembler and use capstone instead.<br>
> <br>
> Best regards,<br>
> Yusuke Suzuki<br>
> _______________________________________________<br>
> webkit-dev mailing list<br>
> <a href="mailto:webkit-dev@lists.webkit.org" target="_blank">webkit-dev@lists.webkit.org</a><br>
> <a href="https://lists.webkit.org/mailman/listinfo/webkit-dev" rel="noreferrer" target="_blank">https://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
</blockquote></div></div>
_______________________________________________<br>jsc-dev mailing list<br><a href="mailto:jsc-dev@lists.webkit.org" target="_blank">jsc-dev@lists.webkit.org</a><br><a href="https://lists.webkit.org/mailman/listinfo/jsc-dev" target="_blank">https://lists.webkit.org/mailman/listinfo/jsc-dev</a><br></div></blockquote></div><br></div></div></div></div></div></blockquote></div></div>