Marcos Slomp
Marcos Slomp
Consider the following: ``` std::map outputs; outputs[Halide::OutputFileType::object] = ...; Halide::compile_standalone_runtime(outputs, target) ``` How do we obtain function symbols from the generated Halide/LLVM object file? How can we produce debug/symbol information...
`D3D12ZoneScope` is calling `tracy::Callstack()` with `depth = 0`, and leads to an assert (in Debug builds): https://github.com/wolfpld/tracy/blob/0721561c547a6deb84d49e16dba0ad620bddbe74/public/tracy/TracyD3D12.hpp#L393 https://github.com/wolfpld/tracy/blob/0721561c547a6deb84d49e16dba0ad620bddbe74/public/tracy/TracyD3D12.hpp#L415 We need a check similar to the one in `VkCtxScope`: https://github.com/wolfpld/tracy/blob/0721561c547a6deb84d49e16dba0ad620bddbe74/public/tracy/TracyVulkan.hpp#L554 This...
At the end of the cmake (Ninja Multi-Config generator) command, I get this: ``` -- Configuring done (124.6s) terminate called after throwing an instance of 'std::out_of_range' what(): map::at Aborted (core...
I think it should be possible, with relatively few changes, to make Tracy a "standalone" sampling-based profiler. Right now, when we setup sampling, we look for activity related to the...
I think we should consider adding an instrumentation directive for Tracy itself, to report internal errors that get "silently ignored". One such example are the various ETW trace API calls,...
This is just a follow-up on the brief discussion we had here: https://github.com/wolfpld/tracy/pull/1125#discussion_r2248801613 I was able to build a client application on Windows via MinGW with both gcc (15.1.0) and...
Switching from the shared (singleton) "NT Kernel Logger" over to private Kernel logging session (Windows 8+). VSync events have also been unified under the same private session and event record...
There's a subtle race condition when threads read `s_sysTraceThread`. Since both the main thread (executing `~Profile()`) and the `Profiler::Worker()` thread call `StopSystemTracing()`, the condition: ``` if (s_sysTraceThread) { ... }...
A handy feature to have is the ability to "embed" into the build information pertaining the conditions which Halide/LLVM was built. (There's `HALIDE_VERSION_*` and `int get_llvm_version();` but that's too janky/coarse/abstract.)...