-
Notifications
You must be signed in to change notification settings - Fork 246
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
rustc_codegen_spirv
taking a long time processing my (large) shader
#851
Comments
After I added codes to my shader, it takes very longer time to compile.
And I added one commit to this in this branch. |
I enabled Procedure
|
I've been working on a $ rg mem2reg 2023-07-08-spirt-disagg-baseline
512:time: 0.011; rss: 187MB -> 187MB ( +0MB) link_block_ordering_pass_and_mem2reg-before-inlining
515:time: 126.704; rss: 189MB -> 158MB ( -31MB) link_block_ordering_pass_and_mem2reg-after-inlining
$ rg qptr::partition_and_propagate 2023-07-08-spirt-disagg-qptr-pnp
538:time: 0.570; rss: 220MB -> 221MB ( +1MB) qptr::partition_and_propagate so that's a 222x speed-up (for the same version of ( EDIT: to be perfectly clear: those flags are not useful without the necessary combination of SPIR-T + Rust-GPU changes and I don't even have an up-to-date Rust-GPU branch anywhere comparable to that one. |
This issue is from Discord conversation https://discordapp.com/channels/750717012564770887/750717499737243679/943879544006381638
Expected Behaviour
I want to compile my shader faster.
Example & Steps To Reproduce
cargo build --release -Z timings
I tested on af3cf2b74e8ef4f4bd98a3cd2cda64b9379d20d7.
In console in VSCode and rust-analyzer plugin. It takes more time.
System Info
The text was updated successfully, but these errors were encountered: