| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
The new function replaces four old functions: set_fragment/vertex/
geometry/compute_sampler_views().
Note: at this time, it's expected that the 'start' parameter will
always be zero.
Reviewed-by: Roland Scheidegger <[email protected]>
Reviewed-by: Marek Olšák <[email protected]>
Tested-by: Emil Velikov <[email protected]>
|
| |
|
|
|
|
| |
Based on the earlier apitrace tracediff.sh script.
|
|
|
|
|
|
| |
- Handle more calls
- Handle more state
- Try to normalize the output a bit, to eliminate spurious differences
|
| |
|
| |
|
|
|
|
|
| |
Cleaned/commented up the code, but forgot to actually test before
commiting...
|
| |
|
|
|
|
| |
Reviewed-by: Brian Paul <[email protected]>
|
|
|
|
|
| |
For TGSI diffing.
Reviewed-by: Brian Paul <[email protected]>
|
|
|
|
|
| |
Copied verbatim from apitrace's scripts/jsondiff.py
Reviewed-by: Brian Paul <[email protected]>
|
|
|
|
|
|
|
| |
Based from the code from the good old python state tracker.
Extremely handy to diagnose regressions in state trackers.
Reviewed-by: Brian Paul <[email protected]>
|
|
|
|
|
| |
To speed up parsing.
Reviewed-by: Brian Paul <[email protected]>
|
|
|
|
|
| |
To get a rough idea of how much time is spent in each gallium driver
function. The time is measured in microseconds.
|
| |
|
|
|
|
| |
Instead of None.
|
|
|
|
|
|
|
|
|
| |
Because:
- bindings are not fully automatic, and they are broken most of the time
- unit tests/samples can be written in C on top of graw
- tracing/retracing is more useful at API levels with stable ABIs such as
GL, producing traces that cover more layers of the driver stack and and
can be used for regression testing
|
|
|