To your list, I can add memory addresses, address calculations, and coordinates.
Do we need an integer multiply? We'll already have a multiplier block for float, and we can route integers through that, but that still means extra logic in the pipeline. We'll also need instructions for converting to/from float. On Wed, May 30, 2012 at 2:43 PM, <[email protected]> wrote: > On Wed, 30 May 2012 14:26:56 -0400, Timothy Normand Miller wrote: >> >> Someone pointed out to me that integer ops don't have much utility in >> GPUs. Memory may be in integer form, but ARGB in 8888 format, for >> instance, would get converted to/from vec4 format (or our equivalent) >> as part of the memory access. If we have no need for integer ops, >> that would simplify the architecture. So can anyone make any >> arguments as to why it would be strictly necessary to support integer >> operations? > > > loop counters ? > compute array indices ? > helpful for crypto acceleration ? > (we're speaking about making an energy-efficient > system so if it means reusing it for other common > tasks, great) > > just wondering. > > > _______________________________________________ > Open-graphics mailing list > [email protected] > http://lists.duskglow.com/mailman/listinfo/open-graphics > List service provided by Duskglow Consulting, LLC (www.duskglow.com) -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
