Bug HLSL preprocessor issue?

Found some weird behavior in ShaderVariables.hlsl:615

Code (CSharp):

1. #define unity_ProbesOcclusion       LoadDOTSInstancedData_ProbesOcclusion()
2. #ifdef PATH1
3. float4 test(){return asfloat(0xFFFF);}
4. #define unity_RenderingLayer        test()
5. #else // PATH2
6. const float4 unity_RenderingLayer = asfloat(0xFFFF);
7. #endif
8. #define unity_MotionVectorsParams   LoadDOTSInstancedData_MotionVectorsParams()
9. #define unity_WorldTransformParams  LoadDOTSInstancedData_WorldTransformParams()
10. #define unity_RendererBounds_Min    LoadDOTSInstancedData_RendererBounds_Min()
11. #define unity_RendererBounds_Max    LoadDOTSInstancedData_RendererBounds_Max()

I replaced LoadDOTSInstancedData_RenderingLayer() with test(). Whenever PATH1 is taken, all meshes become unlit. PATH2 works fine though.

Tried the same in a simple shader and its ok too. Maybe happens only in compute?

Code (CSharp):

1.             float4 test()
2.             {
3.                 return float4(1, 0, 0, 0);
4.             }
5.  
6.             float4 frag2(v2f i) : SV_Target
7.             {
8.                 #define TEST test()
9.                 return float4(TEST.x, 0, 0, 1);
10.             }

 

Thanks for the tip! Indeed preprocessor works fine. The bug is here:

Code (CSharp):

1. asuint(asfloat(0xFFFF)) == 0xFFFF

it returns false (at least on my hardware)

 

yeah, this one does work

Code (CSharp):

1. uint4 LoadDOTSInstancedData_RenderingLayer()
2. {
3.     return 0x0001;
4. }

and this one doesn't

Code (CSharp):

1. float4 LoadDOTSInstancedData_RenderingLayer()
2. {
3.     return asfloat(0x0001);
4. }

considering that this one works too

Code (CSharp):

1. const float4 unity_RenderingLayer = asfloat(0xFFFF);

it seems that asfloat returns different results at compile/run time