| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
src/gallium/auxiliary/pipebuffer/pb_buffer_fenced.c
src/gallium/auxiliary/util/Makefile
src/gallium/drivers/r300/r300_state_derived.c
|
| |
| |
| |
| | |
This reverts commit 5b64d94390e4805e1634f0c8b5e3156e12b8b872.
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
configs/default
src/gallium/auxiliary/pipebuffer/pb_buffer_fenced.c
src/mesa/main/version.h
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I had this patch on my hard drive for long time. It doesn't fully
address SVGA multi-threading issues, but causes no regressions, so decided
to commit while it still applies cleanly.
Attention: merging this into master will cause issues due to recent
changes in reference counting to fix strict aliasing rules violation.
|
| | |
|
| |
| |
| |
| |
| | |
Makes integration of gallium into out of tree components much easier. No
pratical change for components in this tree,
|
| |
| |
| |
| | |
This was discovered by the pipe_reference api change.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Historically, parts of mesa code are not strict-aliasing safe, hence
-fno-strict-aliasing is needed to compile (this got forgotten for scons
builds for gallium, which indeed not only caused compiler warnings but also
unexplicable crashes in non-debug builds). However, we should try to eliminate
code not complying with strict-aliasing code at least for gallium.
Hence change pipe_reference functions to make them strict-aliasing compliant.
This adds a bit more complexity (especially for derived classes) but is the
right thing to do, and it does in fact fix a segfault.
|
|/ |
|
| |
|
|
|
|
| |
It's really just another define. No need for its own header.
|
|\
| |
| |
| |
| |
| | |
Conflicts:
src/gallium/auxiliary/util/u_cpu_detect.c
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
reported by clang static analyzer
|
|
|
|
|
|
|
| |
Avoids warnings on 64bit builds.
Use regular unsigned since that's what gallium expects, but use a
typedef to facilitate possible changes in the future.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This can be almost impossible to avoid - hopefully we won't encounter
a situation where this is a true requirement. Would probably require
drivers to flush between hardware and software vertex processing.
|
|
|
|
| |
Signed-off-by: Alan Coopersmith <[email protected]>
|
| |
|
|
|
|
| |
Signed-off-by: Thomas Hellstrom <thellstrom-at-vmware-dot-com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The core reference counting code is centralized in p_refcnt.h.
This has some consequences related to struct pipe_buffer:
* The screen member of struct pipe_buffer must be initialized, or
pipe_buffer_reference() will crash trying to destroy a buffer with reference
count 0. u_simple_screen takes care of this, but I may have missed some of
the drivers not using it.
* Except for rare exceptions deep in winsys code, buffers must always be
allocated via pipe_buffer_create() or via screen->*buffer_create() rather
than via winsys->*buffer_create().
|
|\
| |
| |
| |
| | |
Conflicts:
src/gallium/auxiliary/pipebuffer/pb_buffer_fenced.c
|
| | |
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
scons/gallium.py
src/gallium/auxiliary/pipebuffer/pb_buffer_fenced.c
src/gallium/include/pipe/p_defines.h
src/mesa/vbo/vbo_exec_api.c
src/mesa/vbo/vbo_exec_draw.c
|
| | |
|
| |
| |
| |
| |
| |
| | |
Conflicts:
src/gallium/auxiliary/pipebuffer/pb_buffer_fenced.c
|
| |
| |
| |
| | |
No real change, as we're not tracking relocations read/write access yet.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
BSD supports pipe in the same way as linux hence options which
are safe for linux are also safe for BSD. Define PIPE_OS_BSD in
include/pipe/p_config.h and adjust the defines to make use of it.
Also define MAP_ANONYMOUS for BSD systems which use MAP_ANON
Signed-off-by: Benjamin Close <[email protected]>
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
src/gallium/auxiliary/pipebuffer/pb_bufmgr_mm.c
src/gallium/auxiliary/util/u_tile.c
|
| | |
|
| |
| |
| |
| |
| | |
It will give the same result 2nd time too, as fencing is done at a
higher level.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The template makefile that most libraries in
gallium included was based on dri and had a bunch
unrelevant junk in it.
Update it and improve the depending makefiles.
|
| |
| |
| |
| |
| | |
The debug functions depend on several util function for os abstractions, and
these depend on debug functions, so a seperate module is not possible.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
move it to pipe/internal/p_winsys_screen.h and start converting
the state trackers to the screen usage
|
|\ \ |
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
allows the driver to overwrite buffer allocation, first step on the way
to making winsys interface internal to the drivers. state trackers and
the code above it will go through the screen
|
| |
| |
| |
| |
| | |
A variation of malloc buffers which get transferred to real graphics memory
when there is an attempt to validate them.
|