Displaying 4 results from an estimated 4 matches for "fxc".
Did you mean:
fc
2011 Mar 29
0
[LLVMdev] [GSoC] "Microsoft Direct3D shader bytecode backend" proposal
...ng D3DCompiler) DLLs. Most games therefore end up using D3DX to
> compile their Direct3D shaders.
>
> Microsoft seems to have paid no attention to optimization of the
> resulting shader code, though. With LLVM, we can do better.
>
Do you have any sources for this? In my experience, fxc is able to do some
clever tricks such as replacing if-then-else conditions with predicated
instructions and swizzles.
>
> By using LLVM's optimizers, programs can potentially generate
> high-performance shader code that works well on the platform on which
> they are running. In ad...
2011 Mar 29
2
[LLVMdev] [GSoC] "Microsoft Direct3D shader bytecode backend" proposal
...st games therefore end up using D3DX to
> compile their Direct3D shaders.
>
> Microsoft seems to have paid no attention to optimization of the
> resulting shader code, though. With LLVM, we can do better.
>
>
> Do you have any sources for this? In my experience, fxc is able to do
> some clever tricks such as replacing if-then-else conditions with
> predicated instructions and swizzles.
I heard rumors that drivers tend not to like highly optimized bytecode
input. But that seems to count against optimization. I could take that
part out.
>
>
>...
2011 Mar 29
3
[LLVMdev] [GSoC] "Microsoft Direct3D shader bytecode backend" proposal
Here's the other of my proposals for this year's Google Summer of Code.
(The first is on cfe-dev.) It was suggested to me by Dan Kegel (from the
Wine project, they really want this).
Title: Microsoft Direct3D shader bytecode backend
Abstract:
There is a distinct lack of open-source frameworks for compiling HLSL,
the shader language used by Direct3D, into bytecode that D3D can
2011 Mar 29
0
[LLVMdev] [GSoC] "Microsoft Direct3D shader bytecode backend" proposal
...using D3DX to
>> compile their Direct3D shaders.
>>
>> Microsoft seems to have paid no attention to optimization of the
>> resulting shader code, though. With LLVM, we can do better.
>>
>>
>> Do you have any sources for this? In my experience, fxc is able to do
>> some clever tricks such as replacing if-then-else conditions with
>> predicated instructions and swizzles.
> I heard rumors that drivers tend not to like highly optimized bytecode
> input. But that seems to count against optimization. I could take that
> part o...