<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 16, 2016, at 5:17 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 dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On 15 September 2016 at 16:54, Matthias Braun <span dir="ltr" class=""><<a href="mailto:matze@braunis.de" target="_blank" class="">matze@braunis.de</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">MatzeB created this revision.<br class="">
MatzeB added a reviewer: rafael.<br class="">
MatzeB added a subscriber: llvm-commits.<br class="">
MatzeB set the repository for this revision to rL LLVM.<br class="">
Herald added a subscriber: mcrosier.<br class="">
<br class="">
r270209 ("Refactor X86 symbol access classification.") broke some EFI firmware projects targetting x86_64-pc-windows-macho. This patch fixes that:<br class="">
<br class=""></blockquote><div class=""><br class=""></div><div class="">So, what exactly does x86_64-pc-windows-macho mean? Is it producing a COFF or a MachO?</div></div></div></div></div></blockquote><div>It is producing a macho file. But as far as I understand it this firmware build does not need and cannot deal with GOT relocations which would not be useful on any current windows system anyway.</div><div><br class=""></div><div>- Matthias</div></div></body></html>