aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorNikita Popov <nikita.ppv@gmail.com>2020-06-23 22:25:04 +0200
committerNikita Popov <nikita.ppv@gmail.com>2020-06-23 22:33:57 +0200
commit6904c7129b26373eb33489b43538ab580829655e (patch)
treeb9f3442cf0acc7f83c82f894cf7d356e3e9fad5a /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parente6d8636935e13f57b52c7dcf81f5c4576e2446f5 (diff)
downloadllvm-6904c7129b26373eb33489b43538ab580829655e.zip
llvm-6904c7129b26373eb33489b43538ab580829655e.tar.gz
llvm-6904c7129b26373eb33489b43538ab580829655e.tar.bz2
[IR] Remove MSVC warning workaround (NFC)
While LLVM does fold this to x+1, GCC does not. As this is hot code, let's try to avoid that. According to https://developercommunity.visualstudio.com/content/problem/211134/unsigned-integer-overflows-in-constexpr-functionsa.html this spurious warning in MSVC has been fixed in Visual Studio 2019 Version 16.4. Let's see if there are any build bots running old MSVC versions with warnings treated as errors...
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions