Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how do I get the fossilize file .foz out of the vulkan driver? #5463

Closed
cmsanta opened this issue May 16, 2024 · 2 comments
Closed

how do I get the fossilize file .foz out of the vulkan driver? #5463

cmsanta opened this issue May 16, 2024 · 2 comments

Comments

@cmsanta
Copy link

cmsanta commented May 16, 2024

detail | 详细描述 | 詳細な説明

Hi, I have the project compiled under UbuntuOS 22.04 LTS with the Intel i915 GPU drivers for a TGL GT2 iGPU. I am interested in getting the fossilize files .foz out of the vulkan compute shaders because I'd like to look at how the compiler generates the IR ASM code for these shaders, however, the .foz files are not getting generated at all. Any idea how to generate the fozz files?

To learn more about Fossilize: https://github.com/ValveSoftware/Fossilize

It's already built-in in the Mesa Library that I have on my system, and all I have to do to generate the .foz file is to export FOSSILIZE=1. I have cross checked that the drivers are running as expected by running a dummy app vulkaninfo and the .foz file gets generated in the same directory where the app was launched.
Any ideas?

@nihui
Copy link
Member

nihui commented May 16, 2024

By default, ncnn uses its own implementation of simplevk to load the vulkan driver. This can avoid some possible dependencies and implement some additional functions for ncnn. However, this is likely to be incompatible with the tool ecosystem based on khronos vulkan loader.
You can use cmake -DNCNN_SIMPLEVK=OFF to compile ncnn to use the system's vulkan loader

https://github.com/Tencent/ncnn/wiki/vulkan-driver-loader

@csanta
Copy link

csanta commented May 23, 2024

Hi @nihui thanks for the quick reply! That's exactly what the issue was. Please go ahead and close this issue.

@nihui nihui closed this as completed May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants