izzy/UnrealEngineUWP
0
0
Fork 0
mirror of https://github.com/izzy2lost/UnrealEngineUWP.git synced 2026-03-26 18:15:20 -07:00
Code Issues Packages Projects Releases Wiki Activity

Disable static analysis warnings for testing against constants.

Browse Source 
#rb none
#jira UE-73187

#ROBOMERGE-OWNER: ben.marsh
#ROBOMERGE-AUTHOR: ben.marsh
#ROBOMERGE-SOURCE: CL 6053421 in //UE4/Release-4.22/... via CL 6053423
#ROBOMERGE-BOT: BUILD (Main -> Dev-Build)

[CL 6058286 by ben marsh in Dev-Build branch]
This commit is contained in:
ben marsh
2019-04-23 13:01:03 -04:00
parent 68c6924b94
commit 79cbebc6eb
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Engine/Source/Runtime/Core/Public/Windows/WindowsPlatformCodeAnalysis.h
View File

@@ -84,7 +84,7 @@
// We don't use exceptions or care to gracefully handle _alloca() failure. Also, we wrap _alloca in an
// appAlloca macro (not inline methods) and don't want to suppress at all call sites.
#pragma warning( disable : 6255 ) // warning C6255: _alloca indicates failure by raising a stack overflow exception. Consider using _malloca instead.
#pragma warning(disable : 6255) // warning C6255: _alloca indicates failure by raising a stack overflow exception. Consider using _malloca instead.
// This a very common false positive warning (but some cases are not false positives!). Disabling for now so that we
// can more quickly see the benefits of static analysis on new code.
@@ -94,6 +94,12 @@
// so we can get the benefits of analysis on cross-platform code sooner.
#pragma warning(disable : 6320) // warning C6320: Exception-filter expression is the constant EXCEPTION_EXECUTE_HANDLER. This might mask exceptions that were not intended to be handled.
// Branching on constants allows us to ensure code paths compile even if they are inactive (eg. if(PLATFORM_FOO){ ... }), and is good practice that should not be discouraged.
#pragma warning(disable : 6326) // warning C6326 : Potential comparison of a constant with another constant.
// Likewise, expressions involving constants can also be valuable to check code paths compile.
#pragma warning(disable : 6240) // warning C6240 : (<expression> && <non-zero constant>) always evaluates to the result of <expression>. Did you intend to use the bitwise-and operator?
//PVS-Studio settings:
//-V::505,542,581,601,668,677,686,688,690,703,704,711,719,720,728,730,735,751,1002,1008
//-V:TRYCOMPRESSION:519,547