<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 10, 2013 at 1:16 PM, Nicolas Cellier <span dir="ltr"><<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><div dir="ltr"><div><div><div><div><div><div>The scheme is currently<br></div>...001 -> immediate int<br></div>
...010 -> immediate char<br></div>...100 -> immediate double<br><br></div>But with 64 bits, 62 remaining for immediate char, that makes many char, well too many compared to Unicode requirements...<br>
</div>What about swapping pattern for char and double? I know it complicates a little bit the 32 <-> 64 image translation, but this gains one more bit for immediate double exponent that is otherwise unused for char.<br>
</div><div>Also, there is room for more immediate values, for example a single precision float.<br>Is there any interest?<br></div></div></blockquote><div><br></div><div>I think an extra bit for immediate double is a good idea. I'm not sure a single precision float immediate is useful given immediate doubles; am I missing something?</div>
</div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>