<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jan 24, 2013, at 12:40 PM, Renato Golin <<a href="mailto:renato.golin@linaro.org">renato.golin@linaro.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">On 24 January 2013 20:33, Chad Rosier <span dir="ltr"><<a href="mailto:mcrosier@apple.com" target="_blank">mcrosier@apple.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Temporarily XFAIL this test; the compiler will segfault if the target-specific<br>
parser is not included in the compiler. Thanks to Renato for discovering the<br>
underlying issue.<br></blockquote><div><br></div><div style="">Hi Chad,</div><div style=""><br></div><div style="">Thanks!</div><div style=""><br></div><div style="">Parser/MicrosoftExtensions.c has the same problem. ;)<br></div><div style="">
<br></div><div style=""><a href="http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/4588">http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/4588</a><br></div><div style=""><br></div><div style="">
I wonder if it was better to mark it only supported on Intel, rather than XFAIL... But I don't remember how LIT does it.</div></div></div></div></blockquote><div><br></div><div>I just went with Daniel's suggestion in clang revision 173367. I'll try to address the underlying issue shortly. Thanks again, Renato.</div><div><br></div><div> Chad</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div style=""><br></div><div style="">--renato</div></div></div></div>
</blockquote></div><br></body></html>