mirror/gcc
2
0
Fork 0
mirror of git://gcc.gnu.org/git/gcc.git synced 2025-04-02 06:40:25 +08:00
Code Issues Packages Projects Releases Wiki Activity

re PR libfortran/49188 (Mismatch between -fsign-zero documentation and formatted output)

Browse Source 
PR libfortran/49188
	PR libfortran/49336
	* invoke.texi: Fix documentation of fsign-zero option. Remove
	contractions.
	* intrinsic.texi: Fix ATAN2 documentation for signed zeros.
	Remove contractions.
	* gfortran.texi: Remove contractions.

From-SVN: r181127
This commit is contained in:
Francois-Xavier Coudert 2011-11-07 22:21:54 +00:00 committed by François-Xavier Coudert
parent 744bbef1e1
commit c5a0818e68
4 changed files with 40 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
gcc/fortran/ChangeLog
View File

@ -1,3 +1,13 @@
2011-11-07 François-Xavier Coudert <fxcoudert@gcc.gnu.org>
PR libfortran/49188
PR libfortran/49336
* invoke.texi: Fix documentation of fsign-zero option. Remove
contractions.
* intrinsic.texi: Fix ATAN2 documentation for signed zeros.
Remove contractions.
* gfortran.texi: Remove contractions.
2011-11-07 Janus Weil <janus@gcc.gnu.org>
PR fortran/50919

26
gcc/fortran/gfortran.texi
View File

@ -222,7 +222,7 @@ compiler.
The GNU Fortran compiler front end was
designed initially as a free replacement for,
or alternative to, the unix @command{f95} command;
@command{gfortran} is the command you'll use to invoke the compiler.
@command{gfortran} is the command you will use to invoke the compiler.
@menu
* About GNU Fortran:: What you should know about the GNU Fortran compiler.
@ -261,7 +261,7 @@ place. The result after compilation of a program is
@dfn{machine code},
code designed to be efficiently translated and processed
by a machine such as your computer.
Humans usually aren't as good writing machine code
Humans usually are not as good writing machine code
as they are at writing Fortran (or C++, Ada, or Java),
because it is easy to make tiny mistakes writing machine code.
@ -580,8 +580,8 @@ Malformed environment variables are silently ignored.
* GFORTRAN_STDOUT_UNIT:: Unit number for standard output
* GFORTRAN_STDERR_UNIT:: Unit number for standard error
* GFORTRAN_TMPDIR:: Directory for scratch files
* GFORTRAN_UNBUFFERED_ALL:: Don't buffer I/O for all units.
* GFORTRAN_UNBUFFERED_PRECONNECTED:: Don't buffer I/O for preconnected units.
* GFORTRAN_UNBUFFERED_ALL:: Do not buffer I/O for all units.
* GFORTRAN_UNBUFFERED_PRECONNECTED:: Do not buffer I/O for preconnected units.
* GFORTRAN_SHOW_LOCUS:: Show location for runtime errors
* GFORTRAN_OPTIONAL_PLUS:: Print leading + where permitted
* GFORTRAN_DEFAULT_RECL:: Default record length for new files
@ -620,7 +620,7 @@ GNU Fortran searches for the environment variable @env{TMP}, then @env{TEMP}.
If these are missing, the default is @file{/tmp}.
@node GFORTRAN_UNBUFFERED_ALL
@section @env{GFORTRAN_UNBUFFERED_ALL}---Don't buffer I/O on all units
@section @env{GFORTRAN_UNBUFFERED_ALL}---Do not buffer I/O on all units
This environment variable controls whether all I/O is unbuffered. If
the first letter is @samp{y}, @samp{Y} or @samp{1}, all I/O is
@ -629,7 +629,7 @@ the first letter is @samp{n}, @samp{N} or @samp{0}, I/O is buffered.
This is the default.
@node GFORTRAN_UNBUFFERED_PRECONNECTED
@section @env{GFORTRAN_UNBUFFERED_PRECONNECTED}---Don't buffer I/O on preconnected units
@section @env{GFORTRAN_UNBUFFERED_PRECONNECTED}---Do not buffer I/O on preconnected units
The environment variable named @env{GFORTRAN_UNBUFFERED_PRECONNECTED} controls
whether I/O on a preconnected unit (i.e.@: STDOUT or STDERR) is unbuffered. If
@ -642,7 +642,7 @@ is @samp{n}, @samp{N} or @samp{0}, I/O is buffered. This is the default.
If the first letter is @samp{y}, @samp{Y} or @samp{1}, filename and
line numbers for runtime errors are printed. If the first letter is
@samp{n}, @samp{N} or @samp{0}, don't print filename and line numbers
@samp{n}, @samp{N} or @samp{0}, do not print filename and line numbers
for runtime errors. The default is to print the location.
@node GFORTRAN_OPTIONAL_PLUS
@ -1953,7 +1953,7 @@ store_catalog(7)%id = 7831
store_catalog(7)%description = "milk bottle"
store_catalog(7)%price = 1.2
! Assignments of a whole variable don't change
! Assignments of a whole variable do not change
store_catalog(12) = pear
print *, store_catalog(12)
@end example
@ -1974,7 +1974,7 @@ print *, store_catalog(12)
@cindex @code{ENCODE}
@cindex @code{DECODE}
GNU Fortran doesn't support the @code{ENCODE} and @code{DECODE}
GNU Fortran does not support the @code{ENCODE} and @code{DECODE}
statements. These statements are best replaced by @code{READ} and
@code{WRITE} statements involving internal files (@code{CHARACTER}
variables and arrays), which have been part of the Fortran standard since
@ -2334,10 +2334,10 @@ Procedure pointers are handled analogously to pointers; the C type is
@code{TYPE(C_FUNPTR)} and the intrinsic conversion procedures are
@code{C_F_PROCPOINTER} and @code{C_FUNLOC}.
Let's consider two examples of actually passing a procedure pointer from
Let us consider two examples of actually passing a procedure pointer from
C to Fortran and vice versa. Note that these examples are also very
similar to passing ordinary pointers between both languages.
First, consider this code in C:
similar to passing ordinary pointers between both languages. First,
consider this code in C:
@smallexample
/* Procedure implemented in Fortran. */
@ -2827,7 +2827,7 @@ some are completely orthogonal to the rest of what is
happening on GNU Fortran,
but others are ``mainstream'' projects in need of enthusiastic hackers.
All of these projects are important!
We'll eventually get around to the things here,
We will eventually get around to the things here,
but they are also things doable by someone who is willing and able.
@menu

18
gcc/fortran/intrinsic.texi
View File

@ -1470,13 +1470,15 @@ If @var{Y} is zero, then @var{X} must be nonzero.
@end multitable
@item @emph{Return value}:
The return value has the same type and kind type parameter as @var{Y}.
It is the principal value of the complex number @math{X + i Y}. If
@var{X} is nonzero, then it lies in the range @math{-\pi \le \atan (x) \leq \pi}.
The return value has the same type and kind type parameter as @var{Y}. It
is the principal value of the complex number @math{X + i Y}. If @var{X}
is nonzero, then it lies in the range @math{-\pi \le \atan (x) \leq \pi}.
The sign is positive if @var{Y} is positive. If @var{Y} is zero, then
the return value is zero if @var{X} is positive and @math{\pi} if @var{X}
is negative. Finally, if @var{X} is zero, then the magnitude of the result
is @math{\pi/2}.
the return value is zero if @var{X} is strictly positive, @math{\pi} if
@var{X} is negative and @var{Y} is positive zero (or the processor does
not handle signed zeros), and @math{-\pi} if @var{X} is negative and
@var{Y} is negative zero. Finally, if @var{X} is zero, then the
magnitude of the result is @math{\pi/2}.
@item @emph{Example}:
@smallexample
@ -2484,7 +2486,7 @@ The return value is of type integer and of the system-dependent kind
number of bytes occupied by the argument. If the argument has the
@code{POINTER} attribute, the number of bytes of the storage area pointed
to is returned. If the argument is of a derived type with @code{POINTER}
or @code{ALLOCATABLE} components, the return value doesn't account for
or @code{ALLOCATABLE} components, the return value does not account for
the sizes of the data pointed to by these components.
@item @emph{Example}:
@ -11467,7 +11469,7 @@ The return value is of type integer and of the system-dependent kind
number of bytes occupied by the argument. If the argument has the
@code{POINTER} attribute, the number of bytes of the storage area pointed
to is returned. If the argument is of a derived type with @code{POINTER}
or @code{ALLOCATABLE} components, the return value doesn't account for
or @code{ALLOCATABLE} components, the return value does not account for
the sizes of the data pointed to by these components. If the argument is
polymorphic, the size according to the declared type is returned. The argument
may not be a procedure or procedure pointer.

14
gcc/fortran/invoke.texi
View File

@ -459,7 +459,7 @@ let the compiler know the current working directory at the time of
preprocessing. When this option is enabled, the preprocessor will emit,
after the initial linemarker, a second linemarker with the current
working directory followed by two slashes. GCC will use this directory,
when it's present in the preprocessed input, as the directory emitted
when it is present in the preprocessed input, as the directory emitted
as the current working directory in some debugging information formats.
This option is implicitly enabled if debugging information is enabled,
but this can be inhibited with the negated form
@ -659,7 +659,7 @@ messages produced.
@item -fsyntax-only
@opindex @code{fsyntax-only}
@cindex syntax checking
Check the code for syntax errors, but don't actually compile it. This
Check the code for syntax errors, but do not actually compile it. This
will generate module files for each module present in the code, but no
other output file.
@ -1088,10 +1088,10 @@ really useful for use by the gfortran testsuite.
@opindex @code{fsign-zero}
When enabled, floating point numbers of value zero with the sign bit set
are written as negative number in formatted output and treated as
negative in the @code{SIGN} intrinsic. @code{fno-sign-zero} does not
print the negative sign of zero values and regards zero as positive
number in the @code{SIGN} intrinsic for compatibility with F77.
Default behavior is to show the negative sign.
negative in the @code{SIGN} intrinsic. @option{-fno-sign-zero} does not
print the negative sign of zero values (or values rounded to zero for I/O)
and regards zero as positive number in the @code{SIGN} intrinsic for
compatibility with Fortran 77. The default is @option{-fsign-zero}.
@end table
@node Code Gen Options
@ -1394,7 +1394,7 @@ The default value for @var{n} is 32768.
@opindex @code{fstack-arrays}
Adding this option will make the fortran compiler put all local arrays,
even those of unknown size onto stack memory. If your program uses very
large local arrays it's possible that you'll have to extend your runtime
large local arrays it is possible that you will have to extend your runtime
limits for stack memory on some operating systems. This flag is enabled
by default at optimization level @option{-Ofast}.