<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 1, 2010, at 1:28 PM, nicolas geoffray wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Chris,<br><br><div class="gmail_quote">On Thu, Apr 1, 2010 at 2:48 AM, Chris Lattner <span dir="ltr"><<a href="mailto:clattner@apple.com">clattner@apple.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
> Machine-generated code often goes over 255 columns. Are you sure you want to design this limitation in?<br>
<br>
</div>Yep. Only clang generates column numbers, and I don't know of any debuggers that do anything with them. We can always change this in the future.<br>
<font color="#888888"><br></font></blockquote><div><br></div><div><br></div><div>Actually, I was using these values (column, line number) to store some runtime informations on an instruction (line number in a Java source file, Java bytecode number, etc). While I know that the interface is somehow not fully defined yet for debug location, having the possibility to get a number of high-level information on a machine instruction through this debugging utility was really useful.</div>
</div></blockquote></div><br><div>Sure, you're welcome to continue doing that with metadata, just don't use the !dbg tag.</div><div><br></div><div>-Chris</div></body></html>