<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 12, 2011, at 6:54 PM, Chris Lattner wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">+1, but should -target be -triple? We can use -target when we have some target/toolchain description mechanism.<br><br></span></blockquote><div><br></div><div>I'm ok here either way. Daniel had expressed a desire for -target so that we could put multiple types of parseable strings here, but I have no dog in this show.</div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><blockquote type="cite">clang -march<br></blockquote><blockquote type="cite">This unfortunate option is around for compatibility, it'll select a sub arch if used from a single architecture compile, error otherwise.<br></blockquote><blockquote type="cite">clang -mcpu<br></blockquote><blockquote type="cite">Ditto.<br></blockquote><br>I think that these should fall into "do whatever gcc does for compatibility" camp.<br></span></blockquote><br></div><div>Agreed. Unfortunately that's definitely a per-target thing for gcc. i.e. mips and arm act differently here :)</div><div><br></div><div>I basically left them in so we could do the best we could for gcc compatibility.</div><div><br></div><div>-eric</div></body></html>