summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/AMDGPU/SILoadStoreOptimizer.cpp
diff options
context:
space:
mode:
authorErik Pilkington <erik.pilkington@gmail.com>2019-03-18 19:23:45 +0000
committerErik Pilkington <erik.pilkington@gmail.com>2019-03-18 19:23:45 +0000
commitb6e16ea006a262c77ed44afc72b94a9b7c9cf440 (patch)
treea632d8849ea69fef6f7564e76ae57b4647512897 /llvm/lib/Target/AMDGPU/SILoadStoreOptimizer.cpp
parent8627178d4680af6a49459659a71f690dfefc2783 (diff)
downloadbcm5719-llvm-b6e16ea006a262c77ed44afc72b94a9b7c9cf440.tar.gz
bcm5719-llvm-b6e16ea006a262c77ed44afc72b94a9b7c9cf440.zip
[Sema] Add some compile time _FORTIFY_SOURCE diagnostics
These diagnose overflowing calls to subset of fortifiable functions. Some functions, like sprintf or strcpy aren't supported right not, but we should probably support these in the future. We previously supported this kind of functionality with -Wbuiltin-memcpy-chk-size, but that diagnostic doesn't work with _FORTIFY implementations that use wrapper functions. Also unlike that diagnostic, we emit these warnings regardless of whether _FORTIFY_SOURCE is actually enabled, which is nice for programs that don't enable the runtime checks. Why not just use diagnose_if, like Bionic does? We can get better diagnostics in the compiler (i.e. mention the sizes), and we have the potential to diagnose sprintf and strcpy which is impossible with diagnose_if (at least, in languages that don't support C++14 constexpr). This approach also saves standard libraries from having to add diagnose_if. rdar://48006655 Differential revision: https://reviews.llvm.org/D58797 llvm-svn: 356397
Diffstat (limited to 'llvm/lib/Target/AMDGPU/SILoadStoreOptimizer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud