|
From: Cary R. <cy...@ya...> - 2008-01-11 18:39:57
|
--- Stephen Williams <st...@ic...> wrote:
> Actually, I think there was an obscure reason for the way it is
> currently. I recall that it's current behavior is used to do some
> specialized part selects in place. For example, if a smaller
> load width N is given, then only the first N bits are loaded.
> This is a common case. It might be that %load/vp0 is not used
> that way, but I'm pretty sure that %load/v is.
I didn't change %load/v so it should be safe. I'll double check %load/vp0
to make sure it's not used in this manner. If it is I think we will have
to add a parameter to pass the value and increase the size of the opcode
table or do the part select a different way. Do you have a preference?
To me increasing the size of the opcode table is the most straight forward
way to solve this if it is a problem. I don't think the increased table
size is that significant.
Other then looking at this I think I'm done.
Cary
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
|