<html><head><base href="x-msg://1263/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 27, 2010, at 10:17 PM, Kiran V wrote:</div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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; "><div bgcolor="#ffffff"><div><font size="2" face="Arial">We are facing a strange problem with Clang compiler (latest version) for ARM Cortex A9.</font></div><div><font size="2" face="Arial"></font> </div><div><font size="2" face="Arial">When we compile our code using arm-linux-gcc compiler, it compiles perfectly and executes perfectly as well.</font></div><div><font size="2" face="Arial">When we compile using clang compiler, it compiles but during execution we see certain floating point values overflow. The program still finishes execution but the final output is wrong.</font></div><div><font size="2" face="Arial"></font> </div><div><font size="2" face="Arial">However on x86, both Clang and gcc give no errors.</font></div><div><font size="2" face="Arial">Since the code base is same we suspect that code generation by clang for ARM is not correct.</font></div><div><font size="2" face="Arial"></font></div></div></span></blockquote></div><br><div>It's certainly possible. It's also possible that your code is doing something invalid and the LLVM optimizers are being more aggressive about exploiting it. If you can provide a test case, we'll look at it.</div><div><br></div><div>John.</div></body></html>