<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 18, 2011, at 2:25 AM, Renato Golin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Verdana; 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; font-size: medium; "><blockquote type="cite">Instead, isn't it easier and straight forward to do a FileCheck on debugger output in the first place ?<br></blockquote><br>Oh, but that is only one level of testing, and it doesn't guarantee<br>your generating correct Dwarf, just "gdb compatible" Dwarf.<br><br>I'm doing all three levels (IR, Dwarf and gdb) and it's much easier to<br>see it fail in the IR level, or even Dwarf than to debug problems<br>using gdb output.<br><br>But I need some better validation for both IR and Dwarf.<br><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></span></blockquote><br></div><div>We have setup to test all these three levels you mention above. All you need is several thousands tests. Do you think that it will show up magically one day ?</div><div>-</div><div>Devang</div></body></html>