| Age | Commit message (Collapse) | Author |
|
* glave-generate.py has moved into tools/glave/scripts/ and renamed to vk-generate.py
* all code-gen'ed files now live in the source tree
* all code-gen'ed files are now generated into a "codegen" directory local to the project to make it easier to spot when a generated file has changed or is being debugged.
* all code-gen'ed files are now being checked in so that we can better track differences caused by the code-gen as the header file evolves.
|
|
|
|
Move almost all linked-lists to unordered_maps and vectors.
Clean up malloc/free with new/delete.
Skip write-strings compile warnings for graphviz_helper.
Still need to migrate the DS update tree to c++.
|
|
|
|
Take advantage of containers, memory allocation, and strings.
|
|
* This way it can be passed to the UI.
* Comment out other XGL_DBG_MSG_UNKNOWN messages so there isn't as much info spew.
|
|
* Currently this is called as part of dump_validation_data(), which is called when the replayer is paused.
|
|
specific; add an entrypoint to print the object lists.
* glvSnapshotPrintObjects() is now exported and causes the tracked objects to get printed out (currently to the console).
** This will be used to help debug the contents of the snapshot as this layer is being developed.
|
|
be converted to a string.
|
|
|
|
ObjectTracker layer.
* Using the ObjectTracker since it already keeps track of the objects being created and destroyed. This is a huge benefit to have as a starting point for the snapshots!
* I've made a few minor changes to ensure the layer gets enabled and the output messages are using a different tag so they can be distinguished from the ObjectTracker.
* Added the new layer to CMakeLists.
|
|
The intel driver currently does only XGL_COORDINATE_ORIGIN_LOWER_LEFT.
Use it for now.
|
|
Use back face culling to confirm that the sense is correct.
|
|
Prevent updates from overwriting xserver-xorg-video-intel and breaking DRI3.
|
|
|
|
Use the py launcher on Windows which understands she bangs
|
|
|
|
|
|
|
|
This reverts commit 10e987d610d43b37556df9b12349f9ffc8cb30c4.
|
|
On windows if multiple python versions installed, then command line args
for python scripts fail. This works around python issue
|
|
Cleaned up MemTracker fence tracking for command buffer completions,
fixed several issues with local fences.
|
|
It is a common case for a command buffer not to have a fence associated
with it -- no reason to call these cases out as errors.
|
|
If CB fence has not completed on call to Begin or Reset CB, flag validation error.
Various improvements to make sure the CB fence is getting reset as appropriate if the fence completes or is destroyed.
|
|
Update struct size codegen to handle callback void* case and ppMemBarriers void** cases conservatively for now.
|
|
|
|
|
|
packet creation
|
|
|
|
|
|
* On Linux debug builds, the asserts cause the debugger to abort, but the code wasn't handling the error case safely anyway, so even a release build would likely crash.
* These situations were being hit if trying to load a trace file from an earlier header version, but are likely to be conditions we'll see when new developers start to use the API.
* With these changes, the error is properly reported and error return values propogated so that the UI detects the invalid file and reports an error to the user.
* The new glv_LogError(..) messages get printed to the console, but are not yet passed to the UI. This will be done as part of a larger change sometime in the future.
|
|
|
|
|
|
Add handling to eliminate meaningless error reporting for the
xglWsiX11CreatePresentableImage memory resources.
|
|
|
|
|
|
|
|
|
|
Update the BUILD.md dependencies in order to build Glave debugger/GUI on
Windows.
|
|
It compiles!
|
|
The only functional change should be that _aligned_malloc() is replaced by
malloc(). It does not seem to matter.
|
|
Remove declarations of
icdDbgRegisterMsgCallback()
icdDbgUnregisterMsgCallback()
icdDbgSetGlobalOption()
|
|
|
|
|
|
Add icd_instance to DRM enumeration functions, and use it for memory
allocation or logging.
|
|
It provides memory allocation and logging support.
|
|
|
|
|
|
The GPU object is not something that is created by the app
and thus object tracker layer does not have to track it.
|
|
|