Open Bug 1620134 Opened 6 years ago Updated 1 year ago

Lack of parallelism when running FXC

Categories

(Firefox Build System :: General, task, P3)

task

Tracking

(Not tracked)

People

(Reporter: glandium, Unassigned)

References

(Blocks 1 open bug)

Details

All the shaders are compiled in a sequence by a single invocation of a single python script. https://searchfox.org/mozilla-central/rev/c79c0d65a183d9d38676855f455a5c6a7f7dadd3/gfx/layers/d3d11/genshaders.py

Priority: -- → P3
Blocks: 1646939
Severity: normal → S3
See Also: → webgpu-fxc

Is this fixed with the landing of bug 1903302 / bug 1940700?

Flags: needinfo?(mh+mozilla)

Those bugs haven't changed the situation wrt generating shaders at build time, but I supposed eventually we'll get rid of FXC?

Flags: needinfo?(mh+mozilla) → needinfo?(nical.bugzilla)

To get rid of FXC entirely we need to move WebRender on Windows from D3D11 to D3D12. It's a long way off but it will happen eventually (the DXC vs FXC for WebGPU thing is separate).

That said, the script this bug is referring to is about old D3D11 layers shaders which I don't think we use anymore so we can likely remove this script.

Flags: needinfo?(nical.bugzilla)

That said, the script this bug is referring to is about old D3D11 layers shaders which I don't think we use anymore so we can likely remove this script.

Nevermind, I looked a bit closer and we are still using these shaders in a specific configuration where web content is rasterized in software with SWGL and composited via the old D3D11 compositor code.

So removing this script is independent from WebRender's usage of D3D11, it's the SWGL + D3D11 compositor configuration that would need to change.

You need to log in before you can comment on or make changes to this bug.