diff options
author | Andy Gibbs <andyg1001@hotmail.co.uk> | 2013-04-17 16:16:16 +0000 |
---|---|---|
committer | Andy Gibbs <andyg1001@hotmail.co.uk> | 2013-04-17 16:16:16 +0000 |
commit | 076eea20b80024fc63bbd71fb019375983680ea6 (patch) | |
tree | 8d42ef66e2730c8cc45f696cc2aa95494c46617d /docs | |
parent | 141f1d24d5aa139ebb91f7ad0252e97a25895fa4 (diff) |
Implemented #pragma GCC warning/error in the same mould as #pragma message.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@179687 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r-- | docs/UsersManual.rst | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/docs/UsersManual.rst b/docs/UsersManual.rst index 97784f1b1b..3dc07aba90 100644 --- a/docs/UsersManual.rst +++ b/docs/UsersManual.rst @@ -652,6 +652,31 @@ supports the GCC pragma, Clang and GCC do not support the exact same set of warnings, so even when using GCC compatible #pragmas there is no guarantee that they will have identical behaviour on both compilers. +In addition to controlling warnings and errors generated by the compiler, it is +possible to generate custom warning and error messages through the following +pragmas: + +.. code-block:: c + + // The following will produce warning messages + #pragma message "some diagnostic message" + #pragma GCC warning "TODO: replace deprecated feature" + + // The following will produce an error message + #pragma GCC error "Not supported" + +These pragmas operate similarly to the ``#warning`` and ``#error`` preprocessor +directives, except that they may also be embedded into preprocessor macros via +the C99 ``_Pragma`` operator, for example: + +.. code-block:: c + + #define STR(X) #X + #define DEFER(M,...) M(__VA_ARGS__) + #define CUSTOM_ERROR(X) _Pragma(STR(GCC error(X " at line " DEFER(STR,__LINE__)))) + + CUSTOM_ERROR("Feature not available"); + Controlling Diagnostics in System Headers ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |