<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 18, 2015 at 10:04 PM, Timothee Cour <span dir="ltr"><<a href="mailto:timothee.cour2+llvm@gmail.com" target="_blank">timothee.cour2+llvm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="font-size:12.8000001907349px">Since llvm doesn't distinguish signed vs unsigned integers anymore, what is the recommended way to represent a language that distinguishes them? </span></div></blockquote><div><br>Distinguishes them how? The IR doesn't have to distinguish everything your source language does.<br><br>If, for example, your language supports overloading based on type (and unsigned and signed types are distinct types), much like Clang does for C++, you would mangle those source-level types into the function name to create distinct functions, regardless of the matching/non-matching nature of the actual argument types.<br><br>Where else do you need to distinguish them?<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="font-size:12.8000001907349px">Is that to introduce new types, eg:</span><div style="font-size:12.8000001907349px">%SignedI32 = type { i32 }<br></div><div style="font-size:12.8000001907349px">%UnsignedI32 = type { i32 }<br></div><div style="font-size:12.8000001907349px">?</div></div>
<br>_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a>         <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
<br></blockquote></div><br></div></div>