diff options
| author | Jacob Keller <jacob.e.keller@intel.com> | 2017-10-17 16:31:36 -0700 |
|---|---|---|
| committer | Christopher Li <sparse@chrisli.org> | 2017-10-19 01:00:27 -0700 |
| commit | c408da27b1a4af23a3cea4fdc54fc41aec4b0f70 (patch) | |
| tree | d3995c435423f8eefac37fcbe863456a4953d346 | |
| parent | cc58fdcfb8569d56e14e97959d42d9305a2b55dd (diff) | |
| download | sparse-dev-c408da27b1a4af23a3cea4fdc54fc41aec4b0f70.tar.gz | |
sparse: document that -Wbitwise is default
In commit commit 02a886bfa3d9 ("Introduce keyword driven
attribute parsing", 2007-03-08) the -Wbitwise keyword was broken and did
not actually work. Instead, bitwise checks were always enabled.
This was fixed by commit commit 0dfda0d1f0fe ("make -Wbitwise
operational again", 2017-02-18) which allowed -Wbitwise and -Wno-bitwise
to work as expected.
However, since -Wbitwise was enabled for so long, that commit changed
the default of -Wbitwise to be enabled, rather than the documented
"disabled".
Fix the documentation to match, and explain that -Wbitwise is enabled by
default and must be disabled.
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Acked-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Signed-off-by: Christopher Li <sparse@chrisli.org>
| -rw-r--r-- | sparse.1 | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -67,8 +67,8 @@ kind of like "NULL" for pointers). So "gfp_t" or the "safe endianness" types would be __bitwise: you can only operate on them by doing specific operations that know about *that* particular type. -Generally, you want bitwise if you are looking for type safety. Sparse -does not issue these warnings by default. +Sparse issues these warnings by default. To turn them off, use +\fB\-Wno\-bitwise\fR. . .TP .B \-Wcast\-to\-as |