Home
last modified time | relevance | path

Searched full:warnings (Results 1 – 25 of 1330) sorted by relevance

12345678910>>...54

/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/perl/files/
H A Dperl-rdepends.txt22 RDEPENDS:perl-module-anydbm-file += "perl-module-warnings"
36 RDEPENDS:perl-module-app-cpan += "perl-module-warnings"
45 RDEPENDS:perl-module-app-prove += "perl-module-warnings"
53 RDEPENDS:perl-module-app-prove-state += "perl-module-warnings"
57 RDEPENDS:perl-module-app-prove-state-result += "perl-module-warnings"
59 RDEPENDS:perl-module-app-prove-state-result-test += "perl-module-warnings"
66 RDEPENDS:perl-module-archive-tar-constant += "perl-module-warnings"
84 RDEPENDS:perl-module-attribute-handlers += "perl-module-warnings"
87 RDEPENDS:perl-module-attributes += "perl-module-warnings"
94 RDEPENDS:perl-module-autodie-exception += "perl-module-warnings"
[all …]
/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/rsync/files/
H A D0001-Turn-on-pedantic-errors-at-the-end-of-configure.patch23 - # Turn pedantic warnings into errors to ensure an array-init overflow is an error.
26 - # Our internal popt code cannot be compiled with pedantic warnings as errors, so try to
27 - # turn off pedantic warnings (which will not lose the error for array-init overflow).
28 - # Older gcc versions don't understand -Wno-pedantic, so check if --help=warnings lists
30 - case `$CC --help=warnings 2>/dev/null | grep Wpedantic` in
50 + # Turn pedantic warnings into errors to ensure an array-init overflow is an error.
53 + # Our internal popt code cannot be compiled with pedantic warnings as errors, so try to
54 + # turn off pedantic warnings (which will not lose the error for array-init overflow).
55 + # Older gcc versions don't understand -Wno-pedantic, so check if --help=warnings lists
57 + case `$CC --help=warnings 2>/dev/null | grep Wpedantic` in
/OK3568_Linux_fs/u-boot/tools/patman/
H A Dcheckpatch.py52 warnings: Number of warnings
57 fields = ['ok', 'problems', 'errors', 'warnings', 'checks', 'lines',
71 # total: 0 errors, 0 warnings, 159 lines checked
73 # total: 0 errors, 2 warnings, 7 checks, 473 lines checked
74 re_stats = re.compile('total: (\\d+) errors, (\d+) warnings, (\d+)')
75 re_stats_full = re.compile('total: (\\d+) errors, (\d+) warnings, (\d+)'
97 result.warnings = int(match.group(2))
152 warning_count += result.warnings
154 print('%d errors, %d warnings, %d checks for %s:' % (result.errors,
155 result.warnings, result.checks, col.Color(col.BLUE, fname)))
[all …]
/OK3568_Linux_fs/buildroot/package/babeltrace2/
H A D0001-configure-simplify-warning-flags-detection.patch8 It unconditionally enables a bunch of warnings we don't want, which
32 --enable-compile-warnings=[no/yes/error]
112 dnl -Wcast-function-type warnings. This warning is present in gcc >= 8. This
128 + [AS_HELP_STRING([--enable-Werror], [Treat compiler warnings as errors.])]
172 -# Check for the presence of an --enable-compile-warnings option to
177 -# Depending on the value of --enable-compile-warnings, different compiler
178 -# warnings are checked to see if they work with the current compiler and,
180 -# allows a consistent set of baseline compiler warnings to be used across
181 -# a code base, irrespective of any warnings enabled locally by individual
182 -# developers. By standardising the warnings used by all developers of a
[all …]
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/as.html/
H A DW.html70 …class="section">2.17 Control Warnings: <samp>-W</samp>, <samp>--warn</samp>, <samp>--no-warn</samp…
75 made. All such warnings are directed to the standard error file.
79 <a name="index-suppressing-warnings"></a>
81 <p>If you use the <samp>-W</samp> and <samp>--no-warn</samp> options, no warnings are issued.
87 <a name="index-errors_002c-caused-by-warnings"></a>
89 <p>If you use the <samp>--fatal-warnings</samp> option, <code>as</code> considers
90 files that generate warnings to be in error.
95 causes warnings to be output as usual.
H A DM32R_002dWarnings.html16 <title>Using as: M32R-Warnings</title>
18 <meta name="description" content="Using as: M32R-Warnings">
19 <meta name="keywords" content="Using as: M32R-Warnings">
69 <a name="M32R-Warnings"></a>
70 <h4 class="subsection">9.21.3 M32R Warnings</h4>
73 <a name="index-M32R-warnings"></a>
80 <dd><p>This message is only produced if warnings for explicit parallel
90 <dd><p>This message is only produced if warnings for explicit parallel
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/as.html/
H A DW.html70 …class="section">2.17 Control Warnings: <samp>-W</samp>, <samp>--warn</samp>, <samp>--no-warn</samp…
75 made. All such warnings are directed to the standard error file.
79 <a name="index-suppressing-warnings"></a>
81 <p>If you use the <samp>-W</samp> and <samp>--no-warn</samp> options, no warnings are issued.
87 <a name="index-errors_002c-caused-by-warnings"></a>
89 <p>If you use the <samp>--fatal-warnings</samp> option, <code>as</code> considers
90 files that generate warnings to be in error.
95 causes warnings to be output as usual.
H A DM32R_002dWarnings.html16 <title>Using as: M32R-Warnings</title>
18 <meta name="description" content="Using as: M32R-Warnings">
19 <meta name="keywords" content="Using as: M32R-Warnings">
69 <a name="M32R-Warnings"></a>
70 <h4 class="subsection">9.21.3 M32R Warnings</h4>
73 <a name="index-M32R-warnings"></a>
80 <dd><p>This message is only produced if warnings for explicit parallel
90 <dd><p>This message is only produced if warnings for explicit parallel
/OK3568_Linux_fs/yocto/meta-openembedded/meta-perl/recipes-perl/libtest/
H A Dlibtest-warnings-perl_0.031.bb5 warnings generated by your tests, combined with the convenience of \
8 be calculated *before* the warnings test is run, resulting in a TAP error. \
15 HOMEPAGE= "https://metacpan.org/release/Test-Warnings"
20 SRC_URI = "https://cpan.metacpan.org/authors/id/E/ET/ETHER/Test-Warnings-${PV}.tar.gz"
24 S = "${WORKDIR}/Test-Warnings-${PV}"
H A Dlibtest-nowarnings-perl_1.04.bb1 SUMMARY = "Make sure you didn't emit any warnings while testing"
2 DESCRIPTION = "In general, your tests shouldn't produce warnings. This \
3 modules causes any warnings to be captured and stored. It automatically \
5 were no warnings. If there were any warings, the test will give a \\"not ok\\" \
9 If some of your tests are supposed to produce warnings then you should \
/OK3568_Linux_fs/yocto/poky/meta/recipes-extended/mc/files/
H A D0001-mc-replace-perl-w-with-use-warnings.patch4 Subject: [PATCH] mc: replace "perl -w" with "use warnings"
16 So replace "perl -w" with "use warnings" to make it work.
18 The man2hlp.in already has "use warnings;", so just remove '-w' is OK.
56 +use warnings;
70 +use warnings;
88 +use warnings;
104 +use warnings;
123 +use warnings;
/OK3568_Linux_fs/kernel/Documentation/RCU/
H A Dstallwarn.rst13 What Causes RCU CPU Stall Warnings?
18 warnings:
77 RCU CPU stall warnings.
80 timeout down to just barely avoid RCU CPU stall warnings, and then
88 result in RCU CPU stall warnings for CONFIG_NO_HZ_COMMON=n kernels.
102 This resulted in a series of RCU CPU stall warnings, eventually
106 Note that SRCU does -not- have CPU stall warnings. Please note that
108 No grace period, no CPU stall warnings.
112 If you have a series of stall warnings from a single extended stall,
166 own warnings, as this often gives better-quality stack traces.
[all …]
/OK3568_Linux_fs/kernel/Documentation/doc-guide/
H A Dcontributing.rst30 Addressing warnings
34 warnings. When you have that many, you might as well have none at all;
36 ones. For this reason, eliminating warnings is one of the highest-priority
41 Warnings issued by a compiler for C code can often be dismissed as false
43 Warnings from the documentation build almost always point at a real
44 problem; making those warnings go away requires understanding the problem
46 warnings should probably not say "fix a warning" in the changelog title;
49 Another important point is that documentation warnings are often created by
51 maintainer appreciates being copied on fixes for these warnings, the
55 For example, in a documentation build I grabbed a pair of warnings nearly
[all …]
/OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/toastergui/templates/
H A Dbuilddashboard.html25 {% if build.warnings.count or build.errors.count %}
32 {% if build.warnings.count %}
34 …<a href="#warnings" class="show-warnings"> {{build.warnings.count}} warning{{build.warnings.count|…
281 {% if build.warnings.count %}
282 <div class="panel panel-default" id="warnings">
286 …le" href="#warning-info" data-toggle="collapse">{{build.warnings.count}} warning{{build.warnings.c…
307 //show warnings section when requested from the previous page
308 if (location.href.search('#warnings') > -1) {
312 //show warnings section when requested from the build outcome
313 $(".show-warnings").click(function() {
/OK3568_Linux_fs/yocto/poky/bitbake/lib/bs4/
H A D__init__.py28 import warnings
90 warnings.warn(
97 warnings.warn(
104 warnings.warn(
111 warnings.warn(
118 warnings.warn(
126 warnings.warn(
164 warnings.warn(self.NO_PARSER_SPECIFIED_WARNING % dict(
177 # Print out warnings for a couple beginner problems
197 warnings.warn(
[all …]
/OK3568_Linux_fs/buildroot/utils/
H A Dcheck-package103 def print_warnings(warnings): argument
105 if warnings is None:
108 for level, message in enumerate(warnings):
115 # Count number of warnings generated and lines processed.
171 # Accumulate number of warnings generated and lines processed.
181 # (e.g. counted by 'wc'), so for stats use stderr. Wait all warnings are
187 print("{} warnings generated".format(total_warnings), file=sys.stderr)
/OK3568_Linux_fs/yocto/poky/meta/recipes-extended/groff/files/
H A D0001-replace-perl-w-with-use-warnings.patch4 Subject: [PATCH 1/2] replace "perl -w" with "use warnings"
16 So replace "perl -w" with "use warnings" to make it work.
46 +use warnings;
64 +use warnings;
82 +use warnings;
100 +use warnings;
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/
H A DError-in-Breakpoints.html29 … href="Breakpoint_002drelated-Warnings.html#Breakpoint_002drelated-Warnings" rel="next" title="Bre…
67 …ef="Breakpoint_002drelated-Warnings.html#Breakpoint_002drelated-Warnings" accesskey="n" rel="next"…
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/
H A DError-in-Breakpoints.html29 … href="Breakpoint_002drelated-Warnings.html#Breakpoint_002drelated-Warnings" rel="next" title="Bre…
67 …ef="Breakpoint_002drelated-Warnings.html#Breakpoint_002drelated-Warnings" accesskey="n" rel="next"…
/OK3568_Linux_fs/kernel/lib/
H A Ddebugobjects.c1033 seq_printf(m, "warnings :%d\n", debug_objects_warnings); in debug_stats_show()
1161 check_results(void *addr, enum debug_obj_state state, int fixups, int warnings) in check_results() argument
1187 if (warnings != debug_objects_warnings) { in check_results()
1188 WARN(1, KERN_ERR "ODEBUG: selftest warnings failed %d != %d\n", in check_results()
1189 warnings, debug_objects_warnings); in check_results()
1213 int fixups, oldfixups, warnings, oldwarnings; in debug_objects_selftest() local
1219 warnings = oldwarnings = debug_objects_warnings; in debug_objects_selftest()
1223 if (check_results(&obj, ODEBUG_STATE_INIT, fixups, warnings)) in debug_objects_selftest()
1226 if (check_results(&obj, ODEBUG_STATE_ACTIVE, fixups, warnings)) in debug_objects_selftest()
1229 if (check_results(&obj, ODEBUG_STATE_ACTIVE, ++fixups, ++warnings)) in debug_objects_selftest()
[all …]
/OK3568_Linux_fs/kernel/tools/testing/selftests/kvm/x86_64/
H A Dmmio_warning_test.c81 int warnings; in get_warnings_count() local
85 if (fscanf(f, "%d", &warnings) < 1) in get_warnings_count()
86 warnings = 0; in get_warnings_count()
89 return warnings; in get_warnings_count()
124 "Warnings found in kernel. Run 'dmesg' to inspect them."); in main()
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/linux/
H A Ddqblk_xfs.h67 __u16 d_iwarns; /* # warnings issued wrt num inodes */
68 __u16 d_bwarns; /* # warnings issued wrt disk blocks */
74 __u16 d_rtbwarns; /* # warnings issued wrt RT disk blks */
104 * warnings are set/cleared by the administrators (or automatically by going
165 __u16 qs_bwarnlimit; /* limit for num warnings */
166 __u16 qs_iwarnlimit; /* limit for num warnings */
210 __u16 qs_bwarnlimit; /* limit for num warnings */
211 __u16 qs_iwarnlimit; /* limit for num warnings */
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/linux/
H A Ddqblk_xfs.h67 __u16 d_iwarns; /* # warnings issued wrt num inodes */
68 __u16 d_bwarns; /* # warnings issued wrt disk blocks */
74 __u16 d_rtbwarns; /* # warnings issued wrt RT disk blks */
104 * warnings are set/cleared by the administrators (or automatically by going
165 __u16 qs_bwarnlimit; /* limit for num warnings */
166 __u16 qs_iwarnlimit; /* limit for num warnings */
210 __u16 qs_bwarnlimit; /* limit for num warnings */
211 __u16 qs_iwarnlimit; /* limit for num warnings */
/OK3568_Linux_fs/yocto/meta-openembedded/meta-perl/recipes-perl/libstrictures/
H A Dlibstrictures-perl_2.000006.bb1 SUMMARY = "strictures - turn on strict and make all warnings fatal"
6 warnings on but don't make them fatal -- which from my point of view is \
7 useless because I want an exception to tell me my code isn't warnings-clean. \
43 perl-module-warnings \
/OK3568_Linux_fs/kernel/tools/testing/ktest/examples/include/
H A Dpatchcheck.conf56 # Instead of just checking for warnings to files that are changed
57 # it can be advantageous to check for any new warnings. If a
59 # touched by the commit. To detect these kinds of warnings, you
65 # warnings file.
74 # and record all the warnings that exist before the patches

12345678910>>...54