<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;"><div>It is more than “verify” . Mach-o has “fat” (aka “universal”) files which contain multiple “slices”. Each slice is for a different arch. The Reader needs to know the intended arch up front to pick the right slice. </div><div><br></div><div><br></div><div><div>On Apr 1, 2014, at 10:06 PM, Rui Ueyama <<a href="mailto:ruiu@google.com">ruiu@google.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr" 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;">I'd think we can simply wait for all files to be parsed and pass them to a LinkingContext to ask whether or not the input file set seems OK.</div></blockquote></div><div><br></div><div>Except there is no method on lld::File that returns its “architecture”. </div><div><br></div><div>We’ve been side stepping the issue of how to model architectures (e.g. triples) in lld. We do need to eventually nail this down because we need to record that info in yaml and native files.</div><div><br></div><div>-Nick</div><div><br></div></body></html>