<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 17, 2011, at 2:33 PM, Nick Lewycky wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; 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; "><div>It can, but that's missing the point :) Clang emits separate file and directory, the .bc has the separate file and directory, we currently join them again here so that the asm stream can split them again. I'm removing that extra join+split pair.</div><div><br></div><div>Going forward, the split could produce different results. I want to encode "clang -isystem foo/bar" + "#include <x/y.h>" into</div><div> directory entry: foo/bar</div><div> file entry: x/y.h</div><div>and there's no way that the resplitting could know that as opposed to "foo" + "bar/x/y.h" and "foo/bar/x" + "y.h".</div><div><br></div><div>Also, this more closely represents what really goes into the debug info, there's a dir entry with the dirname and a file entry which has the filename and the dir entry number.</div></span></blockquote><br></div><div>makes sense!</div><div>-</div><div>Devang</div></body></html>