Lines Matching +refs:clang +refs:format +refs:buffer

3   NOTE: This file is automatically generated by running clang-tblgen
66 acquire_capability (acquire_shared_capability, clang::acquire_capability, clang::acquire_shared_cap…
76 assert_capability (assert_shared_capability, clang::assert_capability, clang::assert_shared_capabil…
241   a future version of clang. Also, the ABI is not standardized and the name
287                              "chosen when the buffer size is known but 'maxlen' is not")))
332 format (gnu::format)
339 Clang supports the ``format`` attribute, which indicates that the function
340 accepts a ``printf`` or ``scanf``-like format string and corresponding
343 Please see `GCC documentation about format attribute
349 #. Clang checks that the function with the ``format`` attribute is called with
350    a format string that uses format specifiers that are allowed, and that
351    arguments match the format string.  This is the ``-Wformat`` warning, it is
354 #. Clang checks that the format string argument is a literal string.  This is
360    fuctions.  Clang does not warn if the format string comes from a function
371        vprintf(s, ap); // warning: format string is not a string literal
374    In this case we warn because ``s`` contains a format string for a
377    If the attribute is removed, clang still warns, because the format string is
392    In this case Clang does not warn because the format string ``s`` and
397 noduplicate (clang::noduplicate)
416   // void nodupfunc() [[clang::noduplicate]];
577 optnone (clang::optnone)
694 release_capability (release_shared_capability, clang::release_capability, clang::release_shared_cap…
704 try_acquire_capability (try_acquire_shared_capability, clang::try_acquire_capability, clang::try_ac…
827 fallthrough (clang::fallthrough)
834 The ``clang::fallthrough`` attribute is used along with the
857     [[clang::fallthrough]];
865       [[clang::fallthrough]];
869     [[clang::fallthrough]]; // warning: fallthrough annotation does not
972   the buffer type matches the passed ``MPI_Datatype``;
1091     struct my_pair *buffer;
1092     MPI_Send(buffer, 1, MPI_DOUBLE_INT /*, ...  */); // no warning
1096     MPI_Send(buffer2, 1, MPI_DOUBLE_INT /*, ...  */); // warning: actual buffer element
1112     MPI_Send(buffer, 1, MPI_DATATYPE_NULL /*, ...  */); // warning: MPI_DATATYPE_NULL
1113                                                         // was specified but buffer