I have this code

float Code(float a,float b, int c)

{

float r=0;

if( c==0)

{

r=a*b;

}

else if( c==1)

{

r=a/b;

}

else if( c==2)

{

r=2*a;

}

return r;

}

Lets say i don't have 3 different "if" but a thousand different "if", and "c" as it is in the code just selects one "if"

Has anyone think about a way to make this faster by creating a way of recompiling the code so it deletes all the unnecessary "if" lines in the assembly code

Or is there anything related to this that solves the problem in a different way?

HLSL supports switches and in my case the "if"s will translate the same way a switch will do to assembly code

don't derail my real question

Has anyone think about a way to make this faster by creating a way of recompiling the code so it deletes all the unnecessary "if" lines in the assembly code while the application runs

Has anyone think about a way to make this faster by creating a way of recompiling the code so it deletes all the unnecessary "if" lines in the assembly code while the application runs

Maybe shader permuation with compile defines?

#ifdef SOMETHING
r = a*b;
#else ifdef SOMETHINGELSE
r = a/b;
#else
r = 2*a;
#endif

Pardon me if I got the actual defines wrong. You can now employ a system, which is called "shader permumations", which will generate for each shader a set of possible compile-define combinations (in that case, a maximum of three). I don't know if this is too complicated/sofisticated for you, you might can up with an easier system based on that, but thats AFAIK the only way to fully eliminate the if-statements.

You can do it with somewhat less code modification like this, but you'll still need to recompile modified source for each shader:

#define c 42
 
float Code(float a,float b)
{
    // original logic stays here
}

this solves what I was asking