Lines Matching full:warnings
167 you want them to be errors rather than warnings). *Note Options
271 errors rather than warnings).
284 `-pedantic-errors' if you want them to be errors rather than warnings).
535 *Note Options to Request or Suppress Warnings: Warning Options.
1082 -msymbol-as-address -mno-inefficient-warnings
1537 `warnings'
1586 --help=warnings,^joined,^undocumented
1928 still contains calls to that function. For example, warnings are
2215 Disable pedantic warnings about constructs used in MFC, such as
2246 warnings. Thus, using `-fpermissive' will allow some
2399 There may also be cases where warnings are emitted even though the
2402 You should rewrite your code to avoid these warnings if you are
2565 filter out those warnings.
2575 Disable warnings when non-templatized friend functions are declared
2818 warnings are not produced if the final stage of compilation is not
2827 compiler will omit such warnings if any differences found are
2906 3.8 Options to Request or Suppress Warnings
2909 Warnings are diagnostic messages that report constructions which are
2914 warnings but control the kinds of diagnostics produced by GCC.
2931 Make all warnings into errors.
2936 warnings controlled by `-Wswitch' into errors. This switch takes a
2938 warnings, for example `-Wno-error=switch' makes `-Wswitch'
2939 warnings not be errors, even when `-Werror' is in effect.
2956 You can request many specific warnings with options beginning `-W',
2957 for example `-Wimplicit' to request warnings on implicit declarations.
2959 beginning `-Wno-' to turn off warnings; for example, `-Wno-implicit'.
2975 Issue all the warnings demanded by strict ISO C and ISO C++;
2990 warnings are also disabled in the expression that follows
3009 dialect is based. Warnings from `-pedantic' are given where they
3011 such warnings to be given only for features not in the specified
3018 warnings.
3021 This enables all the warnings about constructions that some users
3024 enables some language-specific warnings described in *note C++
3162 However, if `-pedantic' is used with `-Wformat', warnings will be
3192 warnings are still given, since the implementation could not know
3216 about, but in future warnings may be added to `-Wformat-security'
3457 provoke warnings when this option is used (even if there is a
3467 provoke warnings when this option is used. The only difference
3600 These warnings occur for individual uninitialized or clobbered
3604 these warnings depend on optimization, the exact variables or
3605 elements for which there are warnings will depend on the precise
3611 warnings are printed.
3618 happen at runtime. These warnings are made optional because GCC is
3642 might be changed by a call to `longjmp'. These warnings as well
3651 Some spurious warnings can be avoided if you declare all the
3659 understood by GCC. If this command line option is used, warnings
3661 This is not the case if the warnings were only enabled by the
3723 warning levels are defined. No warnings are issued for the use of
3791 Warnings from system headers are normally suppressed, on the
3794 command line option tells GCC to emit warnings from system headers
3856 macros in user code might normally lead to spurious warnings,
3885 `__STDC__' to avoid missing initializer warnings and relies
3891 This is a subset of the possible conversion warnings, for the
3962 number of warnings triggered by intentional shadowing.
3983 Disables the warnings about non-ISO `printf' / `scanf' format
4042 non-`const' `char *' pointer will get a warning. These warnings
4047 these warnings.
4064 like in `abs (2.0)'. Warnings about conversions between signed
4071 base class or a reference to them. Warnings about conversions
4107 other warnings of `-Wextra' without this warning, use `-Wextra
4147 suppresses warnings for redefinition of `__TIMESTAMP__',
4184 not declared in header files. In C++, no warnings are issued for
4203 warnings without this one, use `-Wextra
4293 warnings without this one, use `-Wextra -Wno-override-init'.
4354 can cause the warnings produced by `-Winline' to appear or
4358 Suppress warnings from applying the `offsetof' macro to a non-POD
4372 Suppress warnings from casts to pointer type of an integer of a
4385 Suppress warnings from casts from a pointer to an integer type of a
4434 Suppress warnings about constructs that cannot be instrumented by
4647 silence warnings, and omitting other options that would cause
8812 Turns on all optional warnings which are desirable for normal code.
8815 expressions. Note that many of the preprocessor's warnings are on
8829 newlines produce warnings inside a comment.
8833 trigraph conversion without warnings, but get the other `-Wall'
8834 warnings, use `-trigraphs -Wall -Wno-trigraphs'.
8880 Make all warnings into hard errors. Source code which triggers
8881 warnings will be rejected.
8884 Issue warnings for code in system headers. These are normally
8890 Suppress all warnings, including those which GNU CPP issues by
8901 GCC issues without `-pedantic' but treats as warnings.
8925 Passing `-M' to the driver implies `-E', and suppresses warnings
9234 report correct column numbers in warnings or errors, even if tabs
11117 code: no warnings or errors are generated when call-saved
14994 `-mno-inefficient-warnings'
14995 Disables warnings about the generation of inefficient code. These
14996 warnings can be generated, for example, when compiling code which
20435 should do instead. Note that the warnings only occurs for uses:
20660 `vsprintf' whenever such warnings are requested (using
21165 code. More importantly, it helps avoid spurious warnings of
21416 The warnings for missing or incorrect sentinels are enabled with
23052 they should do instead. Note that the warnings only occur for
26235 `-pedantic' and other options cause warnings for many GNU C extensions.
26236 You can prevent such warnings within one expression by writing
26481 invoke undefined behavior at runtime. Warnings for out of bound
37761 produce warnings for the listed variables. The effect is similar
37918 warnings. Or, a project might selectively enable diagnostics and treat
37923 diagnostics are modifiable; at the moment only warnings (normally
41001 * Warnings and Errors:: Which problems in your code get warnings,
41132 * GCC compiled code sometimes emits warnings from the HP-UX
41138 These warnings are harmless and can be safely ignored.
41419 standards, then your programs might get warnings (especially when using
41803 File: gcc.info, Node: Non-bugs, Next: Warnings and Errors, Prev: C++ Misunderstandings, Up: Trouble
42013 * Making certain warnings into errors by default.
42023 turn these warnings into errors.
42027 File: gcc.info, Node: Warnings and Errors, Prev: Non-bugs, Up: Trouble
42033 warnings. Each kind has a different purpose:
42039 "Warnings" report other unusual conditions in your code that _may_
42045 Warnings may indicate danger points where you should check to make sure
42048 warnings are issued only if you ask for them, with one of the `-W'
42049 options (for instance, `-Wall' requests a variety of useful warnings).
42056 The `-pedantic' option tells GCC to issue warnings in such cases;
42058 mean that _all_ non-ISO constructs get warnings or errors.
42060 *Note Options to Request or Suppress Warnings: Warning Options, for
42096 unless the compiler reports errors (not just warnings) which would
43598 * Michael Cook for libstdc++ cleanup patches to reduce warnings.
43728 warnings and assorted bug fixes.
46693 * pedantic: Warnings and Errors.
46698 * pedantic-errors <4>: Warnings and Errors.
47744 * error messages: Warnings and Errors.
48113 * longjmp warnings: Warning Options. (line 738)
48156 * messages, warning and error: Warnings and Errors.
48246 * options to control warnings: Warning Options. (line 6)
48529 * suppressing warnings: Warning Options. (line 6)
48535 * system headers, warnings from: Warning Options. (line 887)
48779 * warnings from system headers: Warning Options. (line 887)
48780 * warnings vs errors: Warnings and Errors.
49082 Node: Warnings and Errors1743408
