| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
shader/shader program objects to avoid memory access error.
|
|
|
|
| |
This reverts commit 3ffd11f71d021f672b9bc15b3c39c155a0e2fecb.
|
| |
|
| |
|
|
|
|
| |
This bug was introduced by commit 978145a075255ae153ee05c2a037400e61558079.
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
names.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The PVS_VECTOR_OPCODE macro should be modified to support macro instructions,
too.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The VE_MULTIPLY_ADD has further restrictions on reading temporary memory which
may complicate things. See AMD's documentation.
|
| |
| |
| |
| |
| |
| | |
This opcode is likely a mistake from reverse engineering. MAD_2 isn't included
in AMD's documentation, and my testing reviles there is no problem using the
documented MAD opcode.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|