<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 29, 2010, at 4:08 PM, Xinliang David Li wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">On Fri, Oct 29, 2010 at 3:54 PM, Chris Lattner <span dir="ltr"><<a href="mailto:clattner@apple.com">clattner@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div><div class="im"><div>On Oct 29, 2010, at 11:35 AM, Xinliang David Li wrote:</div><blockquote type="cite">Thanks for the -m tip to pass llvm options. Why is it not documented anywhere. See <a href="http://clang.llvm.org/docs/UsersManual.html#commandline" target="_blank">http://clang.llvm.org/docs/UsersManual.html#commandline</a></blockquote>
<div><br></div></div>-mllvm flags are somewhat equivalent to gcc -param options. -mllvm flags are for compiler hackers to play with, and are not stable or documented. Once TBAA is stable and reliable it will be controlled with -fstrict-aliasing as you'd expect.</div>
<div><br></div></div></blockquote><div><br></div><div>-mllvm is also useful for passing options like -print-after=xxx. May be it should be mentioned when invoking 'clang --help-hidden'.</div></div></blockquote><br></div><div>But that's another example of something for compiler hackers, which isn't stable or documented :-)</div><div><br></div><div>-Chris</div><br></body></html>