FreeChainXenon/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[doc] Reword description of -Wno-absolute-value

Browse source 
2019-02-27  Martin Jambor  <mjambor@suse.cz>
	    Martin Sebor  <msebor@redhat.com>

	* doc/invoke.texi (Warning Options): Reword description of
	-Wno-absolute-value.


Co-Authored-By: Martin Sebor <msebor@redhat.com>

From-SVN: r269246
This commit is contained in:
Martin Jambor 2019-02-27 11:07:01 +01:00 • committed by Martin Jambor
parent 65b309f7a5
commit 736da58676
2 changed files with 13 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
gcc/ChangeLog
View file

@ -1,3 +1,9 @@
2019-02-27 Martin Jambor <mjambor@suse.cz>
Martin Sebor <msebor@redhat.com>
* doc/invoke.texi (Warning Options): Reword description of
-Wno-absolute-value.
2019-02-27 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/89280

10
gcc/doc/invoke.texi
View file

@ -6656,9 +6656,13 @@ example, warn if an unsigned variable is compared against zero with
@item -Wabsolute-value @r{(C and Objective-C only)}
@opindex Wabsolute-value
@opindex Wno-absolute-value
Warn when a wrong absolute value function seems to be used or when it
does not have any effect because its argument is an unsigned type.
This warning be suppressed with an explicit type cast and it is also
Warn for calls to standard functions that compute the absolute value
of an argument when a more appropriate standard function is available.
For example, calling @code{abs(3.14)} triggers the warning because the
appropriate function to call to compute the absolute value of a double
argument is @code{fabs}. The option also triggers warnings when the
argument in a call to such a function has an unsigned type. This
warning can be suppressed with an explicit type cast and it is also
enabled by @option{-Wextra}.
@include cppwarnopts.texi