Search Issue Tracker
Fixed
Fixed in 2021.3.14f1, 2022.1.23f1, 2022.2.0a10
Votes
1
Found in
2021.3.11f1
2022.1.21f1
2022.2.0a9
Issue ID
UUM-18025
Regression
No
Multiple C4717 warning in Unity.RenderPipelines.Universal.Runtime2.cpp
How to reproduce:
1. Open the user's attached project
2. Build the project for UWP, iOS or any other IL2CPP platform where you can see C++ compiler output
3. Observe build warnings:
1>il2cppOutput\Unity.RenderPipelines.Universal.Runtime2.cpp(15003): warning C4717: 'UniversalRenderPipelineAsset_set_additionalLightsShadowResolutionTierHigh_mAFE0532328839F34DE18FFCB03079EBFFD0A1206': recursive on all control paths, function will cause runtime stack overflow
1>il2cppOutput\Unity.RenderPipelines.Universal.Runtime2.cpp(14963): warning C4717: 'UniversalRenderPipelineAsset_set_additionalLightsShadowResolutionTierLow_mC81357DB56D34D63D90EDD8C88839628858B815C': recursive on all control paths, function will cause runtime stack overflow
1>il2cppOutput\Unity.RenderPipelines.Universal.Runtime2.cpp(15270): warning C4717: 'UniversalRenderPipelineAsset_set_cascadeBorder_mC2D3A4B6764C0018D925BE49D1CFD1F458E4F13C': recursive on all control paths, function will cause runtime stack overflow
Expected results: No "C4717: recursive on all control paths, function will cause runtime stack overflow" warnings in the Visual Studio console
Reproducible with: 2021.3.11f1, 2022.2.0a9
Not reproducible with: 2020.3.41f1, 2022.2.0a10, 2022.2.0b10, 2023.1.0a16
Reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Add comment