<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I submitted a patch to have llvm-bcanalyzer print the wrapper.</div><div class=""><br class=""></div><div class=""><a href="http://reviews.llvm.org/D16642" rel="noreferrer" target="_blank" style="color: rgb(17, 85, 204); font-family: arial, sans-serif; font-size: 12.8px; line-height: normal; widows: 1; background-color: rgb(255, 255, 255);" class="">http://reviews.llvm.org/D16642</a></div><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 26, 2016, at 9:38 AM, Rafael Espíndola <<a href="mailto:rafael.espindola@gmail.com" class="">rafael.espindola@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">I think it would also be fine to teach the llvm-bcanalyzer to emit this, even if it's behind a flag to do so.<br class=""><br class=""></blockquote><br class="">Good point. Since it is normally used with FileCheck it can probably<br class="">just always print a first line saying if it seeing a warper or a plain<br class="">bitcode.<br class=""><br class="">Cheers,<br class="">Rafael<br class=""></div></div></blockquote></div><br class=""></body></html>