search for: _check_return_

Displaying 3 results from an estimated 3 matches for "_check_return_".

2016 Sep 02
2
Adding [[nodiscard]] to Compiler.h
...and [[clang::warn_unused_result]] to be used on a class this way, with equivalent affects, so it'd be nice to use that if we aren't building in C++17 mode. We already have a LLVM_UNUSED_RESULT defined to this, but AFAICT gcc only allows it on function declarations, and the MSVC equivalent (_Check_return_) seems like it's not allowed on types either. I guess we want a new macro LLVM_NODISCARD, that's [[nodiscard]] if available, else [[clang::warn_unused_result]] if we're clang (maybe even clang 3.6 and up, I'm not sure if it works before that), else empty. Thoughts?
2020 Aug 15
5
Supporting libunwind on Windows 10 (32bit; 64bit) for MSVC and Clang
..._SECURE_NO_WARNINGS. See online help for details. [-Wdeprecated-declarations] log = (getenv("LIBUNWIND_PRINT_APIS") != NULL); ^ C:\Program Files\Windows Kits\10\include\10.0.18362.0\ucrt\stdlib.h:1190:20: note: 'getenv' has been explicitly marked deprecated here _Check_return_ _CRT_INSECURE_DEPRECATE(_dupenv_s) ^ C:\Program Files\Microsoft Visual Studio\2019\Preview\VC\Tools\MSVC\14.27.29109\include\vcruntime.h:320:55: note: expanded from macro '_CRT_INSECURE_DEPRECATE' #define _CRT_INSECURE_DEPRECATE(_Replacement) _CRT_DEPRECATE_TEXT(...
2016 Sep 02
2
Adding [[nodiscard]] to Compiler.h
...on a class this way, with equivalent affects, so it'd be nice to >> use that if we aren't building in C++17 mode. >> >> We already have a LLVM_UNUSED_RESULT defined to this, but AFAICT gcc >> only allows it on function declarations, and the MSVC equivalent >> (_Check_return_) seems like it's not allowed on types either. I guess we >> want a new macro LLVM_NODISCARD, that's [[nodiscard]] if available, else >> [[clang::warn_unused_result]] if we're clang (maybe even clang 3.6 and >> up, I'm not sure if it works before that), else empty....