<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Dec 25, 2011, at 6:42 PM, Joe Groff wrote:</div><blockquote type="cite">On Sunday, December 25, 2011, Eli Friedman <<a href="mailto:eli.friedman@gmail.com">eli.friedman@gmail.com</a>> wrote:<br><br>> Yes... unfortunately, that case wasn't clear in the original standard,<br>> and versions of gcc from before that clarification implement generate<br>
> the same code you're seeing from clang. clang uses the old gcc<br>> behavior on OSX, and the spec-compliant behavior on other platforms.<br>> If you're interested in the relevant code in clang, search for<br>
> honorsRevision0_98 in lib/CodeGen/TargetInfo.cpp.<br>><br>> -Eli<br><br>Thanks for the reference, Eli. Out of curiosity, is this platform-specific behavior documented anywhere other than the gcc and clang source? Apple's documentation states that Mac OS X follows AMD's spec, without qualification.<br></blockquote></div><br><div>We're aware of the discrepancy and are making an effort to resolve it.</div><div><br></div><div>John.</div></body></html>