[Mesa-dev] TGSI ISA formalization

[Corbin Simpson]

On Thu, Jun 17, 2010 at 1:59 AM, Zack Rusin <zackr at vmware.com> wrote:
>
> That doesn't make much sense to me, all those sets contain portion if not
> everything from the other set. If anything the instructions should be divided
> into something like:
> 1) move
> 2) arithmetic
>   - integer
>   - floating point
>   - double
> 3) bitwise
> 4) resource access (sampling, tex instructions, ld etc done in the resources branch)
> 5) raster instructions (e.g. kill)
> 6) conditions (sge etc.)
> 7) control flow (bgnloop, call, end, if etc)
> 8) primitives (emit, end_primitivive)
> 9) type conversion
>
> Figuring out which state trackers use which for what purposes is a different problem.
> It could be noted in the instructions docs what uses it, but I doubt we'll be able to keep
> that up to date.

I like the bitwise, flow control, and primitive groups. My main
concern is splitting things into groups that make it easy to say, "Oh
yes, this hardware supports all of these opcodes." Also, we have a
*lot* of opcodes. Any kind of grouping based on the semantics of the
opcodes is going to be useful.

-- 
When the facts change, I change my mind. What do you do, sir? ~ Keynes

Corbin Simpson
<MostAwesomeDude at gmail.com>