AnsweredAssumed Answered

CodeXL: Static analysis of compiled HLSL (DirectX Byte-Code/DXBC)

Question asked by optimiz3 on Feb 1, 2016
Latest reply on Feb 22, 2016 by optimiz3

Right now CodeXL 1.9 offers static analysis of HLSL shaders through a build pipeline that looks like this:


1. Input HLSL

2. DirectX compiles HLSL to DXBC

3. DXBC is fed into analysis tool


However, our shaders are massive and the HLSL takes between 15-30 minutes to compile.  The generated DXBC output is anywhere form 256KB to 1MB depending on the shader.


It would save a TON of time if CodeXL could load the DXBC file directly rather than forcing a 15-30 minute compile every time, and would also let us verify production binaries as we only ship compiled DXBC with our software as is mandated by Microsoft (for Windows Store apps).


Is there a way to skip the HLSL compilation step and have CodeXL direcly load the DXBC for analyses?  Seeing as the AMD driver only cares about the compiled DXBC this an extremely critical feature for reproducability and verifiability.


Our shaders are scientific and cryptographic compute functions that run on top of DirectX - it would be great if we could improve our AMD support.