<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 18, 2010, at 10:01 PMPDT, Roberto Bagnara wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>Testing clang against GCC's test suite results into several<br>violated assertions. Are you interested in receiving bug<br>reports for those?</div></blockquote><div><br></div><div>Yes, thanks.</div><br><blockquote type="cite"><div>*******************************************************************<br>float-range-1.c<br>*******************************************************************<br>[Thread 1] APFloat.cpp:161: int readExponent(const char*, const char*): Assertion failed: p == end && "Invalid exponent in exponent"<br>Stack dump:<br>0. float-range-1.c:12:13: current parser token '1e+100000000f'<br>1. float-range-1.c:11:1: parsing function body 'f'<br>2. float-range-1.c:11:1: in compound statement ('{}')<br>Aborted (core dumped)<br></div></blockquote><br></div><div>I fixed this one, 111534. Incidentally, gcc-4.2 warns on this only with -pedantic, while clang warns by default. Is that intentional?</div><div><br></div><div><blockquote type="cite"><font class="Apple-style-span" color="#000000"></font></blockquote><blockquote type="cite"><font class="Apple-style-span" color="#6278FF"><font class="Apple-style-span" color="#152DFF">*****************************************************************<br>c99-hexfloat-3.c<br>*******************************************************************<br>[Thread 1] APFloat.cpp:2248: llvm::APFloat::opStatus llvm::APFloat::convertFromHexadecimalString(llvm::StringRef, llvm::APFloat::roundingMode): Assertion failed: (dot == end || p - begin != 1) && "Significand has no digits"<br>Stack dump:<br>0. c99-hexfloat-3.c:16:13: current parser token '0x.p0'<br>Aborted (core dumped)</font><br></font></blockquote><br></div><div>clang is correct to reject this although of course it should not crash. Generally APFloat expects correct input and asserts if it doesn't find it, so the fix should probably be upstream.</div><div><br></div></body></html>