<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 25 Aug 2017, at 17:26, Kostya Serebryany <<a href="mailto:kcc@google.com" class="">kcc@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><br class="Apple-interchange-newline"><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="gmail_quote" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On Fri, Aug 25, 2017 at 8:51 AM, Daniel Sanders<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:daniel_l_sanders@apple.com" target="_blank" class="">daniel_l_sanders@apple.com</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">(removed my @<a href="http://imgtec.com/" rel="noreferrer" target="_blank" class="">imgtec.com</a><span class="Apple-converted-space"> </span>address since it no longer exists)<br class=""><br class="">Sorry for the slow reply, it's a busy time for me right now.<br class=""><span class=""><br class="">> On 23 Aug 2017, at 00:21, George Karpenkov via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class="">><br class="">> Hi,<br class="">><br class="">> As a part of a recent move of libFuzzer from LLVM to compiler-rt I am looking into updating the build code<br class="">> for the libraries which use libFuzzer.<br class="">><br class="">> I have tried to compile llvm-mc-assemble-fuzzer, and llvm-mc-disassemble-fuzzer, and I couldn’t build either of those.<br class="">> For the first one, the reason is that it refers to a nonexistent enum,<br class=""><br class=""></span>I don't seem to be able to build this with cmake+ninja yet (I'm having trouble recursing the compiler on macOS) but after manually building it... It seems this broke at the start of August when the CodeModel argument was removed from InitMCObjectFileInfo(). After removing that argument and adding an 'extern "C"' it at least compiles. I haven't had chance to try running it yet.<br class=""><span class=""><br class="">> and for the second one I believe the reason is that it does not enclose LLVMFuzzerTestOneInput in “extern ‘C’”.<br class=""><br class=""></span>I agree we need an "extern C" here. I'm not sure what changed to make it required though.<br class=""><span class=""><br class="">> Are those libraries maintained and/or used?<br class=""><br class=""></span>I haven't used it for quite a while now. My original motivator was the Mips assembler/disassembler being very buggy. I was using it to find crashes and generate interesting test cases for round-trip testing of the assembler/disassembler. Since then, the Mips MC layer has become much more stable and I've also changed jobs.<br class=""><br class="">That said, I'd like to set up a bot to make use of these tools,<span class="Apple-converted-space"> </span></blockquote><div class=""><br class=""></div><div class="">As soon as these fuzz targets build, don't immediately crash, and have someone who cares about them, </div><div class="">I can add them to OSS-Fuzz for automated continuous fuzzing. </div></div></div></blockquote><div><br class=""></div><div>I had an out-of-tree target in mind but it would be great to test the in-tree targets with OSS-Fuzz.</div><br class=""><blockquote type="cite" class=""><div class=""><div class="gmail_quote" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">it's mostly a matter of finding time for it. That's normally difficult but I should be able to do that in the next few weeks.<br class=""><span class="im HOEnZb"><br class="">> If yes, the code should be compilable, and ideally there should be a buildbot.<br class="">> If no, maybe we should remove it, or move it to a separate repository.<br class="">><br class="">> Thanks,<br class="">> George<br class="">><br class="">> (sorry for starting multiple threads, I believe this way it is more convenient to keep track of tasks)<br class=""></span><div class="HOEnZb"><div class="h5">> ______________________________<wbr class="">_________________<br class="">> LLVM Developers mailing list<br class="">><span class="Apple-converted-space"> </span><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">><span class="Apple-converted-space"> </span><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/<wbr class="">mailman/listinfo/llvm-dev</a></div></div></blockquote></div></div></blockquote></div><br class=""></body></html>