<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Sep 3, 2013, at 11:06 AM, Rui Ueyama <<a href="mailto:ruiu@google.com">ruiu@google.com</a>> wrote:</div><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div dir="ltr">Nick, does Mach-O need symbol aliasing to be handled in the linker?</div></div></blockquote><div>Yes. The darwin linker has command line options for adding aliases. </div><div><br></div><div>Back when I first started working on the darwin linker, a big complaint from the compiler team was that mach-o did not support aliases like ELF did, so the compiler team kept having to special case lots of test cases and functionality that used __attribute__((alias(“xx”))) on darwin.</div><div><br></div><div>-Nick</div><div><br></div><br><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div dir="ltr"><div><br></div><div>If ELF, Mach-O and COFF don't need to handle symbol aliasing in the linker, I'd conclude symbol aliasing is not actually what need, and remove isAlias() and such from DefinedAtom. And if that's the case (if we don't need symbol aliasing in the linker), I think my original patch would make more sense.</div></div></div></blockquote></div></body></html>