From 886472548b851d20e6006ea86aa929107ed95c27 Mon Sep 17 00:00:00 2001 From: jb Date: Mon, 7 Feb 2011 19:02:01 +0000 Subject: [PATCH] texinfo fixes suggested by Ralf Wildenhues git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@169892 138bc75d-0d04-0410-961f-82ee72b054a4 --- gcc/fortran/ChangeLog | 6 ++++++ gcc/fortran/gfortran.texi | 16 ++++++++-------- gcc/fortran/intrinsic.texi | 23 ++++++++++++----------- 3 files changed, 26 insertions(+), 19 deletions(-) diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index e514dce078e..4463c8d5e38 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,9 @@ +2011-02-07 Janne Blomqvist + Ralf Wildenhues + + * gfortran.texi (Thread-safety): texinfo styling fixes. + * intrinsic.texi: Likewise. + 2011-02-06 Janne Blomqvist * gfortran.texi (Compiler Characteristics): Add reference to diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi index 035dbd74879..16fea025c8f 100644 --- a/gcc/fortran/gfortran.texi +++ b/gcc/fortran/gfortran.texi @@ -1168,25 +1168,25 @@ using OpenMP, by calling OS thread handling functions via the @code{ISO_C_BINDING} facility, or by GNU Fortran compiled library code being called from a multi-threaded program. -The GNU Fortran runtime library, (@var{libgfortran}), supports being +The GNU Fortran runtime library, (@code{libgfortran}), supports being called concurrently from multiple threads with the following exceptions. -During library initialization, the C @code{getenv()} function is used, -which need not be thread-safe. Similarly, the @code{getenv()} +During library initialization, the C @code{getenv} function is used, +which need not be thread-safe. Similarly, the @code{getenv} function is used to implement the @code{GET_ENVIRONMENT_VARIABLE} and @code{GETENV} intrinsics. It is the responsibility of the user to ensure that the environment is not being updated concurrently when any of these actions are taking place. The @code{EXECUTE_COMMAND_LINE} and @code{SYSTEM} intrinsics are -implemented with the @code{system()} function, which need not be +implemented with the @code{system} function, which need not be thread-safe. It is the responsibility of the user to ensure that -@code{system()} is not called concurrently. +@code{system} is not called concurrently. -Finally, for platforms not supporting thread-safe @code{POSIX} -functions, further functionality might not be thread-safe. For -details, please consult the documentation for your operating system. +Finally, for platforms not supporting thread-safe POSIX functions, +further functionality might not be thread-safe. For details, please +consult the documentation for your operating system. @c --------------------------------------------------------------------- @c Extensions diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi index ea5528fe111..925b0afcbda 100644 --- a/gcc/fortran/intrinsic.texi +++ b/gcc/fortran/intrinsic.texi @@ -4151,10 +4151,11 @@ end program test_etime asynchronously. The @code{COMMAND} argument is passed to the shell and executed, using -the C library's @code{system()} call. (The shell is @code{sh} on Unix -systems, and @code{cmd.exe} on Windows.) If @code{WAIT} is present and -has the value false, the execution of the command is asynchronous if the -system supports it; otherwise, the command is executed synchronously. +the C library's @code{system} call. (The shell is @code{sh} on Unix +systems, and @code{cmd.exe} on Windows.) If @code{WAIT} is present +and has the value false, the execution of the command is asynchronous +if the system supports it; otherwise, the command is executed +synchronously. The three last arguments allow the user to get status information. After synchronous execution, @code{EXITSTAT} contains the integer exit code of @@ -4162,9 +4163,9 @@ the command, as returned by @code{system}. @code{CMDSTAT} is set to zero if the command line was executed (whatever its exit status was). @code{CMDMSG} is assigned an error message if an error has occurred. -Note that the @code{system()} call need not be thread-safe. It is the -responsibility of the user to ensure that @code{system()} is not -called concurrently. +Note that the @code{system} call need not be thread-safe. It is the +responsibility of the user to ensure that @code{system} is not called +concurrently. @item @emph{Standard}: Fortran 2008 and later @@ -4204,7 +4205,7 @@ end program test_exec @item @emph{Note}: -Because this intrinsic is implemented in terms of the @code{system()} +Because this intrinsic is implemented in terms of the @code{system} function call, its behavior with respect to signaling is processor dependent. In particular, on POSIX-compliant systems, the SIGINT and SIGQUIT signals will be ignored, and the SIGCHLD will be blocked. As @@ -11791,9 +11792,9 @@ and environment-dependent. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. -Note that the @code{system()} call need not be thread-safe. It is the -responsibility of the user to ensure that @code{system()} is not -called concurrently. +Note that the @code{system} call need not be thread-safe. It is the +responsibility of the user to ensure that @code{system} is not called +concurrently. @item @emph{Standard}: GNU extension -- 2.11.0