On 21 April 2013 20:56, Timothy Normand Miller <[email protected]> wrote: > Someone on IRC pointed out that 16 bits for the shift amount for e.g. SHLI > is overkill. What more interesting thing can we do there? Did someone > suggest that we combine all of those shifts to use one opcode? Or maybe > they should be put into the opcode 0 space. > > So many suggestions, I lose track. What can we do that is smarter here?
Quick thoughts: reduce the size of the immediate value and use the extra bits for the 'type' of shift: - ZEXT/SEXT - shift/rotate - NOT prior to shift -- Eitan Adler _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
