<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 19, 2011, at 4:42 PM, Nick Lewycky wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">This is a follow-up to the thread that started here:<div> <a href="http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110725/125101.html">http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110725/125101.html</a></div>
<div><br></div><div>Would anyone object to a flag "-fdwarf-compilation-dir=..." clang flag that would clobber the DW_AT_comp_dir setting?</div></blockquote><div><br></div>My first reaction is to resist such flag. It is most likely solving the wrong problem. IMO, DW_AT_comp_dir is something whose existence no compiler user needs to know.</div><div><br><blockquote type="cite"><div>This is a gcc compatibility issue for us as we're relying on our ability to control this part of the debug output by setting $PWD. A flag would also work for me.</div>
</blockquote><br></div><div>Can you elaborate ? What is exactly missing in clang's debug output today ? and how does it differ from gcc ? and why does it matter ?</div><div><br></div><div>-</div><div>Devang</div><br></body></html>