In the API event handler we want to share information between the core
layer and the API. Specifically, around associating various ids with
different kinds of events. For example, associate render pass id with
draw ids, or command buffer ids with draw ids.
---
.../drivers/swr/rasterizer/archrast/a
---
src/gallium/drivers/swr/rasterizer/jitter/builder_mem.cpp | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/drivers/swr/rasterizer/jitter/builder_mem.cpp
b/src/gallium/drivers/swr/rasterizer/jitter/builder_mem.cpp
index 67e415c..6fa60a1 100644
--- a/src/gallium/drivers/swr/raste
This is useful for archrast data collection. This greatly speeds up the
post processing script since there is significantly less events generated.
Finally, this is a simpler option to communicate to users than having
them directly adjust MAX_PRIMS_PER_DRAW and MAX_TESS_PRIMS_PER_DRAW.
---
.../dri
Removed specific split draw events.
---
.../drivers/swr/rasterizer/archrast/archrast.cpp | 22 ++
.../drivers/swr/rasterizer/archrast/events.proto | 4
.../swr/rasterizer/archrast/events_private.proto | 20
src/gallium/drivers/swr/rasterizer/cor
Supports popcnt on vector masks (e.g. <8 x i1>)
---
src/gallium/drivers/swr/rasterizer/jitter/builder_misc.cpp | 8
src/gallium/drivers/swr/rasterizer/jitter/builder_misc.h | 1 +
2 files changed, 9 insertions(+)
diff --git a/src/gallium/drivers/swr/rasterizer/jitter/builder_misc.cpp
---
src/gallium/drivers/swr/rasterizer/archrast/archrast.cpp | 6 +++---
src/gallium/drivers/swr/rasterizer/archrast/events.proto | 1 +
src/gallium/drivers/swr/rasterizer/archrast/events_private.proto | 2 ++
src/gallium/drivers/swr/rasterizer/core/api.cpp | 4 ++-
---
src/gallium/drivers/swr/rasterizer/jitter/builder_mem.h | 3 ++-
src/gallium/drivers/swr/rasterizer/jitter/fetch_jit.cpp | 7 ++-
2 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/src/gallium/drivers/swr/rasterizer/jitter/builder_mem.h
b/src/gallium/drivers/swr/rasterizer/jit
- Incorporate flatshade flag into the shader generation
- Use provoking vertex (vc) in shader when flat shading.
---
src/gallium/drivers/swr/swr_shader.cpp | 4
src/gallium/drivers/swr/swr_shader.h | 1 +
2 files changed, 5 insertions(+)
diff --git a/src/gallium/drivers/swr/swr_shader.cpp
There is a limit of 10 display connections, which was a
problem for apps/tests that were continuously opening/closing display
connections.
This fix uses XAddExtension() and XESetCloseDisplay() to keep track
of the status of the display connections from the X server, freeing
mesa-related data as X
There is a limit of 10 display connections, which was a
problem for apps/tests that were continuously opening/closing display
connections.
This fix uses XAddExtension() and XESetCloseDisplay() to keep track
of the status of the display connections from the X server, freeing
mesa-related data as X
There is a limit of 10 display connections, which was a
problem for apps/tests that were continuously opening/closing display
connections.
This fix uses XAddExtension() and XESetCloseDisplay() to keep track
of the status of the display connections from the X server, freeing
mesa-related data as X
This resolves some order dependencies between the already existing
callback the newly created one.
---
src/gallium/state_trackers/glx/xlib/glx_api.c | 1 +
src/gallium/state_trackers/glx/xlib/xm_api.c | 58 +++
src/gallium/state_trackers/glx/xlib/xm_api.h | 3 ++
3 file
screen may still be used by other resources that are not yet freed.
To correctly fix this there will be a need to account for resources
differently, but this quick fix is not any worse than the original
code that leaked screens anyway.
---
src/gallium/state_trackers/glx/xlib/xm_api.c | 10 +++-
Removed bound_to_context. We now pick up the context from the screen
instead of the resource itself. The resource could be out-of-date
and point to a pipe that is already freed.
Fixes manywin mesa xdemo.
---
src/gallium/drivers/swr/swr_context.cpp | 16 +++-
src/gallium/drivers/swr/
301 - 314 of 314 matches
Mail list logo
