<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 30, 2012, at 8:51 PM, Chandler Carruth wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Mon, Jan 30, 2012 at 10:08 AM, James Molloy <span dir="ltr"><<a href="mailto:james.molloy@arm.com">james.molloy@arm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-GB" link="blue" vlink="purple">
<div><p class="MsoNormal"><span style="color:#1f497d">Hi Chandler,<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#1f497d">One point:<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#1f497d">+ /// Note that this tests for
16-bit pointer width, and nothing else.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#1f497d">I’m not sure this comment is
accurate. For example, real mode x86 would be 16-bit but has 24-bit pointers
(seg:offset).</span></p></div></div></blockquote><div><br></div><div>As far as I can tell, there is no support for x86-16 or real mode or any of the other segmented addressing modes on x86. If such modes are added, I would be quite happy for them to return false on all three of these queries. ;] I still think "pointer size" is the most descriptive term, but I'm open to more suggestions.</div>
<div><br></div><div>FWIW, the reason I don't particularly like "native width of the register file" is that i find it much less clear and unambiguous given the diversity of register widths on even modern architectures. However, addresses generally have a fixed size on modern architectures, and so that seems a good classification scheme.</div>
</div></blockquote><br></div><div>Just my contribution to the bikeshed: I don't think that it makes sense for llvm::Triple to know the "native width of the register file", since that is such an amorphous statement. The best that llvm::Triple can know is sizeof(void*) in the default address space.</div><div><br></div><div>-Chris</div><br></body></html>