CPU_SET.3, INFINITY.3, __ppc_get_timebase.3, __ppc_set_ppr_med.3, __ppc_yield.3, __setfpucw.3, acos.3, acosh.3, adjtime.3, aio_fsync.3, aio_init.3, aio_read.3, aio_return.3, aio_suspend.3, aio_write.3, alloca.3, argz_add.3, asin.3, asinh.3, asprintf.3, assert.3, assert_perror.3, atan.3, atan2.3, atanh.3, atexit.3, backtrace.3, basename.3, bindresvport.3, bsd_signal.3, bsearch.3, bswap.3, btree.3, byteorder.3, bzero.3, canonicalize_file_name.3, carg.3, cbrt.3, ccos.3, ccosh.3, ceil.3, cexp.3, clearenv.3, clock.3, clog.3, clog10.3, clog2.3, confstr.3, copysign.3, cos.3, cosh.3, crypt.3, csin.3, csinh.3, csqrt.3, ctan.3, ctanh.3, ctime.3, dbopen.3, dl_iterate_phdr.3, dladdr.3, dlerror.3, dlinfo.3, dlopen.3, dlsym.3, drand48_r.3, duplocale.3, encrypt.3, end.3, endian.3, envz_add.3, erf.3, erfc.3, err.3, errno.3, error.3, euidaccess.3, exec.3, exp.3, exp10.3, exp2.3, expm1.3, fabs.3, fcloseall.3, fdim.3, fenv.3, ferror.3, fexecve.3, fflush.3, ffs.3, fgetc.3, finite.3, floor.3, fma.3, fmax.3, fmemopen.3, fmin.3, fmod.3, fmtmsg.3, fopen.3, fopencookie.3, fpclassify.3, fpurge.3, fputwc.3, fputws.3, frexp.3, fseek.3, fseeko.3, ftime.3, fts.3, ftw.3, futimes.3, gamma.3, gcvt.3, get_nprocs_conf.3, get_phys_pages.3, getaddrinfo.3, getaddrinfo_a.3, getauxval.3, getcwd.3, getdate.3, getentropy.3, getenv.3, getfsent.3, getgrent_r.3, getgrnam.3, getgrouplist.3, gethostbyname.3, gethostid.3, getifaddrs.3, getline.3, getlogin.3, getmntent.3, getnameinfo.3, getnetent.3, getnetent_r.3, getopt.3, getprotoent.3, getprotoent_r.3, getpw.3, getpwent.3, getpwent_r.3, getpwnam.3, getrpcent.3, getrpcent_r.3, getrpcport.3, gets.3, getservent.3, getservent_r.3, getspnam.3, getsubopt.3, getttyent.3, getutent.3, getwchar.3, glob.3, gnu_get_libc_version.3, grantpt.3, gsignal.3, hash.3, hsearch.3, hypot.3, iconv.3, iconv_close.3, iconv_open.3, if_nameindex.3, if_nametoindex.3, ilogb.3, inet.3, inet_net_pton.3, inet_ntop.3, initgroups.3, insque.3, intro.3, isalpha.3, isgreater.3, j0.3, key_setsecret.3, killpg.3, ldexp.3, lgamma.3, lio_listio.3, lockf.3, log.3, log10.3, log1p.3, log2.3, logb.3, login.3, lrint.3, lround.3, lsearch.3, lseek64.3, makecontext.3, makedev.3, mallinfo.3, malloc_get_state.3, malloc_info.3, malloc_stats.3, malloc_trim.3, malloc_usable_size.3, mallopt.3, matherr.3, mbsnrtowcs.3, mbsrtowcs.3, mcheck.3, memccpy.3, memchr.3, memcmp.3, memcpy.3, mkfifo.3, mkstemp.3, mktemp.3, modf.3, mpool.3, mq_close.3, mq_getattr.3, mq_notify.3, mq_open.3, mq_receive.3, mq_send.3, mtrace.3, newlocale.3, nextafter.3, nextup.3, nl_langinfo.3, ntp_gettime.3, offsetof.3, on_exit.3, open_memstream.3, opendir.3, openpty.3, perror.3, popen.3, posix_fallocate.3, posix_madvise.3, posix_memalign.3, posix_openpt.3, posix_spawn.3, pow.3, printf.3, profil.3, program_invocation_name.3, psignal.3, pthread_atfork.3, pthread_attr_init.3, pthread_attr_setaffinity_np.3, pthread_attr_setdetachstate.3, pthread_attr_setguardsize.3, pthread_attr_setinheritsched.3, pthread_attr_setschedparam.3, pthread_attr_setschedpolicy.3, pthread_attr_setscope.3, pthread_attr_setstack.3, pthread_attr_setstackaddr.3, pthread_attr_setstacksize.3, pthread_cancel.3, pthread_cleanup_push.3, pthread_cleanup_push_defer_np.3, pthread_create.3, pthread_detach.3, pthread_exit.3, pthread_getattr_default_np.3, pthread_getattr_np.3, pthread_getcpuclockid.3, pthread_join.3, pthread_kill.3, pthread_kill_other_threads_np.3, pthread_self.3, pthread_setaffinity_np.3, pthread_setcancelstate.3, pthread_setconcurrency.3, pthread_setname_np.3, pthread_setschedparam.3, pthread_sigmask.3, pthread_sigqueue.3, pthread_testcancel.3, pthread_tryjoin_np.3, ptsname.3, putgrent.3, putpwent.3, qsort.3, random.3, random_r.3, rcmd.3, re_comp.3, readdir.3, realpath.3, recno.3, regex.3, remainder.3, remove.3, remquo.3, resolver.3, rexec.3, rint.3, round.3, rpc.3, rpmatch.3, rtime.3, scalb.3, scalbln.3, scandir.3, scanf.3, sem_close.3, sem_destroy.3, sem_getvalue.3, sem_init.3, sem_open.3, sem_wait.3, setbuf.3, setenv.3, setlocale.3, setlogmask.3, setnetgrent.3, shm_open.3, signbit.3, significand.3, sigpause.3, sigqueue.3, sigset.3, sigvec.3, sin.3, sincos.3, sinh.3, sleep.3, sockatmark.3, sqrt.3, statvfs.3, stdarg.3, stdin.3, strcasecmp.3, strcat.3, strchr.3, strcoll.3, strcpy.3, strdup.3, strerror.3, strfmon.3, strfromd.3, strftime.3, strptime.3, strsignal.3, strstr.3, strtod.3, strtok.3, strtol.3, strtoul.3, syslog.3, system.3, sysv_signal.3, tan.3, tanh.3, telldir.3, tempnam.3, termios.3, tgamma.3, timeradd.3, tmpnam.3, toupper.3, towlower.3, towupper.3, trunc.3, tzset.3, ualarm.3, ulimit.3, undocumented.3, unlocked_stdio.3, updwtmp.3, uselocale.3, usleep.3, wcrtomb.3, wcsdup.3, wcsnrtombs.3, wcsrtombs.3, wcstombs.3, wctob.3, wcwidth.3, wordexp.3, wprintf.3, xcrypt.3, xdr.3, y0.3: Formatting fix: replace blank lines with .PP/.IP

Blank lines shouldn't generally appear in *roff source (other
than in code examples), since they create large vertical
spaces between text blocks.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man3/CPU_SET.3

@@ -83,14 +83,14 @@ data structure represents a set of CPUs.
 CPU sets are used by
 .BR sched_setaffinity (2)
 and similar interfaces.
-
+.PP
 The
 .I cpu_set_t
 data type is implemented as a bit mask.
 However, the data structure treated as considered opaque:
 all manipulation of CPU sets should be done via the macros
 described in this page.
-
+.PP
 The following macros are provided to operate on the CPU set
 .IR set :
 .TP 17
@@ -139,7 +139,7 @@ The constant
 (currently 1024) specifies a value one greater than the maximum CPU
 number that can be stored in
 .IR cpu_set_t .
-
+.PP
 The following macros perform logical operations on CPU sets:
 .TP 17
 .BR CPU_AND ()
@@ -182,7 +182,7 @@ size CPU sets (e.g., to allocate sets larger than that
 defined by the standard
 .I cpu_set_t
 data type), glibc nowadays provides a set of macros to support this.
-
+.PP
 The following macros are used to allocate and deallocate CPU sets:
 .TP 17
 .BR CPU_ALLOC ()
@@ -219,27 +219,27 @@ return nonzero if
 is in
 .IR set ;
 otherwise, it returns 0.
-
+.PP
 .BR CPU_COUNT ()
 and
 .BR CPU_COUNT_S ()
 return the number of CPUs in
 .IR set .
-
+.PP
 .BR CPU_EQUAL ()
 and
 .BR CPU_EQUAL_S ()
 return nonzero if the two CPU sets are equal; otherwise they return 0.
-
+.PP
 .BR CPU_ALLOC ()
 returns a pointer on success, or NULL on failure.
 (Errors are as for
 .BR malloc (3).)
-
+.PP
 .BR CPU_ALLOC_SIZE ()
 returns the number of bytes required to store a
 CPU set of the specified cardinality.
-
+.PP
 The other functions do not return a value.
 .SH VERSIONS
 The
@@ -249,10 +249,10 @@ The
 and
 .BR CPU_ISSET ()
 macros were added in glibc 2.3.3.
-
+.PP
 .BR CPU_COUNT ()
 first appeared in glibc 2.6.
-
+.PP
 .BR CPU_AND (),
 .BR CPU_OR (),
 .BR CPU_XOR (),
@@ -275,14 +275,14 @@ These interfaces are Linux-specific.
 .SH NOTES
 To duplicate a CPU set, use
 .BR memcpy (3).
-
+.PP
 Since CPU sets are bit masks allocated in units of long words,
 the actual number of CPUs in a dynamically
 allocated CPU set will be rounded up to the next multiple of
 .IR "sizeof(unsigned long)" .
 An application should consider the contents of these extra bits
 to be undefined.
-
+.PP
 Notwithstanding the similarity in the names,
 note that the constant
 .B CPU_SETSIZE
@@ -294,7 +294,7 @@ while the
 argument of the
 .BR CPU_*_S ()
 macros is a size in bytes.
-
+.PP
 The data types for arguments and return values shown
 in the SYNOPSIS are hints what about is expected in each case.
 However, since these interfaces are implemented as macros,
@@ -315,7 +315,7 @@ These bugs are fixed in glibc 2.9.
 .SH EXAMPLE
 The following program demonstrates the use of some of the macros
 used for dynamically allocated CPU sets.
-
+.PP
 .nf
 #define _GNU_SOURCE
 #include <sched.h>

man3/INFINITY.3

@@ -47,7 +47,7 @@ The macro
 expands to a
 .I float
 constant representing positive infinity.
-
+.PP
 The macro
 .B NAN
 expands to a
@@ -62,7 +62,7 @@ The opposite is a
 .I signaling
 NaN.
 See IEC 60559:1989.
-
+.PP
 The macros
 .BR HUGE_VAL ,
 .BR HUGE_VALF ,

man3/__ppc_get_timebase.3

@@ -39,7 +39,7 @@ reads the current value of the Time Base Register and returns its
 value, while
 .BR __ppc_get_timebase_freq ()
 returns the frequency in which the Time Base Register is updated.
-
+.PP
 The Time Base Register is a 64-bit register provided by Power Architecture
 processors.
 It stores a monotonically incremented value that is updated at a
@@ -49,7 +49,7 @@ frequency.
 .BR __ppc_get_timebase ()
 returns a 64-bit unsigned integer that represents the current value of the
 Time Base Register.
-
+.PP
 .BR __ppc_get_timebase_freq ()
 returns a 64-bit unsigned integer that represents the frequency at
 which the Time Base Register is updated.

man3/__ppc_set_ppr_med.3

@@ -129,5 +129,5 @@ Availability of these functions can be tested using
 .BR "#ifdef _ARCH_PWR8" .
 .SH SEE ALSO
 .BR __ppc_yield (3)
-
+.PP
 .IR "Power ISA, Book\ II - Section\ 3.1 (Program Priority Registers)"

man3/__ppc_yield.3

@@ -80,5 +80,5 @@ T}	Thread safety	MT-Safe
 These functions are nonstandard GNU extensions.
 .SH SEE ALSO
 .BR __ppc_set_ppr_med (3)
-
+.PP
 .IR "Power ISA, Book\ II - Section\ 3.2 (""or"" architecture)"

man3/__setfpucw.3

@@ -50,7 +50,7 @@ macros from
 can be used.
 .SH EXAMPLE
 .B __setfpucw(0x1372)
-
+.PP
 Set FPU control word on the i386 architecture to
 .br
      \- extended precision

man3/acos.3

@@ -70,22 +70,22 @@ the value whose cosine is
 On success, these functions return the arc cosine of
 .IR x
 in radians; the return value is in the range [0,\ pi].
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is +1,
 +0 is returned.
-
+.PP
 If
 .I x
 is positive infinity or negative infinity,
 a domain error occurs,
 and a NaN is returned.
-
+.PP
 If
 .I x
 is outside the range [\-1,\ 1],
@@ -122,7 +122,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/acosh.3

@@ -79,19 +79,19 @@ that is the value whose hyperbolic cosine is
 .SH RETURN VALUE
 On success, these functions return the inverse hyperbolic cosine of
 .IR x .
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is +1, +0 is returned.
-
+.PP
 If
 .I x
 is positive infinity, positive infinity is returned.
-
+.PP
 If
 .I x
 is less than 1,
@@ -128,7 +128,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/adjtime.3

@@ -70,7 +70,7 @@ has been completed.
 If the adjustment in
 .I delta
 is negative, then the clock is slowed down in a similar fashion.
-
+.PP
 If a clock adjustment from an earlier
 .BR adjtime ()
 call is already in progress
@@ -80,7 +80,7 @@ call, and
 .I delta
 is not NULL for the later call, then the earlier adjustment is stopped,
 but any already completed part of that adjustment is not undone.
-
+.PP
 If
 .I olddelta
 is not NULL, then the buffer that it points to is used to return
@@ -130,7 +130,7 @@ to adjust the time prevents the problems that can be caused for certain
 applications (e.g.,
 .BR make (1))
 by abrupt positive or negative jumps in the system time.
-
+.PP
 .BR adjtime ()
 is intended to be used to make small adjustments to the system time.
 Most systems impose a limit on the adjustment that can be specified in

man3/aio_fsync.3

@@ -55,7 +55,7 @@ is
 .BR O_DSYNC ,
 this call is the asynchronous analog of
 .BR fdatasync (2).
-
+.PP
 Note that this is a request only; it does not wait for I/O completion.
 .LP
 Apart from

man3/aio_init.3

@@ -42,7 +42,7 @@ function allows the caller to provide tuning hints to the
 glibc POSIX AIO implementation.
 Use of this function is optional, but to be effective,
 it must be called before employing any other functions in the POSIX AIO API.
-
+.PP
 The tuning information is provided in the buffer pointed to by the argument
 .IR init .
 This buffer is a structure of the following form:

man3/aio_read.3

@@ -38,9 +38,9 @@ function queues the I/O request described by the buffer pointed to by
 This function is the asynchronous analog of
 .BR read (2).
 The arguments of the call
-
+.PP
     read(fd, buf, count)
-
+.PP
 correspond (in order) to the fields
 .IR aio_fildes ,
 .IR aio_buf ,
@@ -151,7 +151,7 @@ The buffer area being read into
 .\" or the control block of the operation
 must not be accessed during the operation or undefined results may occur.
 The memory areas involved must remain valid.
-
+.PP
 Simultaneous I/O operations specifying the same
 .I aiocb
 structure produce undefined results.

man3/aio_return.3

@@ -56,7 +56,7 @@ or
 .BR fdatasync (2),
 call.
 On error, \-1 is returned, and \fIerrno\fP is set appropriately.
-
+.PP
 If the asynchronous I/O operation has not yet completed,
 the return value and effect of
 .BR aio_return ()

man3/aio_suspend.3

@@ -122,13 +122,13 @@ POSIX.1-2001, POSIX.1-2008.
 One can achieve polling by using a non-NULL
 .I timeout
 that specifies a zero time interval.
-
+.PP
 If one or more of the asynchronous I/O operations specified in
 .IR aiocb_list
 has already completed at the time of the call to
 .BR aio_suspend (),
 then the call returns immediately.
-
+.PP
 To determine which I/O operations have completed
 after a successful return from
 .BR aio_suspend (),

man3/aio_write.3

@@ -38,9 +38,9 @@ function queues the I/O request described by the buffer pointed to by
 This function is the asynchronous analog of
 .BR write (2).
 The arguments of the call
-
+.PP
     write(fd, buf, count)
-
+.PP
 correspond (in order) to the fields
 .IR aio_fildes ,
 .IR aio_buf ,
@@ -156,7 +156,7 @@ The buffer area being written out
 .\" or the control block of the operation
 must not be accessed during the operation or undefined results may occur.
 The memory areas involved must remain valid.
-
+.PP
 Simultaneous I/O operations specifying the same
 .I aiocb
 structure produce undefined results.

man3/alloca.3

@@ -76,7 +76,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 This function is not in POSIX.1.
-
+.PP
 There is evidence that the
 .BR alloca ()
 function appeared in 32V, PWB, PWB.2, 3BSD, and 4BSD.
@@ -97,7 +97,7 @@ it can also simplify memory deallocation in applications that use
 or
 .BR siglongjmp (3).
 Otherwise, its use is discouraged.
-
+.PP
 Because the space allocated by
 .BR alloca ()
 is allocated within the stack frame,
@@ -106,7 +106,7 @@ is jumped over by a call to
 .BR longjmp (3)
 or
 .BR siglongjmp (3).
-
+.PP
 Do not attempt to
 .BR free (3)
 space allocated by
@@ -154,7 +154,7 @@ There is no error indication if the stack frame cannot be extended.
 (However, after a failed allocation, the program is likely to receive a
 .B SIGSEGV
 signal if it attempts to access the unallocated space.)
-
+.PP
 On many systems
 .BR alloca ()
 cannot be used inside the list of arguments of a function call, because

man3/argz_add.3

@@ -223,7 +223,7 @@ T{
 .BR argz_stringify ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 These functions are a GNU extension.
 Handle with care.

man3/asin.3

@@ -71,16 +71,16 @@ that is the value whose sine is
 On success, these functions return the principal value of the arc sine of
 .IR x
 in radians; the return value is in the range [\-pi/2,\ pi/2].
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is +0 (\-0),
 +0 (\-0) is returned.
-
+.PP
 If
 .I x
 is outside the range [\-1,\ 1],
@@ -120,7 +120,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/asinh.3

@@ -79,15 +79,15 @@ that is the value whose hyperbolic sine is
 .SH RETURN VALUE
 On success, these functions return the inverse hyperbolic sine of
 .IR x .
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is +0 (\-0), +0 (\-0) is returned.
-
+.PP
 If
 .I x
 is positive infinity (negative infinity),
@@ -113,7 +113,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/asprintf.3

@@ -71,7 +71,7 @@ T{
 .BR vasprintf ()
 T}	Thread safety	MT-Safe locale
 .TE
-
+.sp 1
 .SH CONFORMING TO
 These functions are GNU extensions, not in C or POSIX.
 They are also available under *BSD.

man3/assert.3

@@ -38,7 +38,7 @@ assert \- abort the program if assertion is false
 This macro can help programmers find bugs in their programs,
 or handle exceptional cases
 via a crash that will produce limited debugging output.
-
+.PP
 If
 .I expression
 is false (i.e., compares equal to zero),
@@ -50,9 +50,9 @@ The error message includes the name of the file and function containing the
 .BR assert ()
 call, the source code line number of the call, and the text of the argument;
 something like:
-
+.PP
     prog: some_file.c:16: some_func: Assertion `val == 0' failed.
-
+.PP
 If the macro
 .B NDEBUG
 is defined at the moment
@@ -80,7 +80,7 @@ T{
 .BR assert ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 POSIX.1-2001, POSIX.1-2008, C89, C99.
 In C89,

man3/assert_perror.3

@@ -68,7 +68,7 @@ T{
 .BR assert_perror ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 This is a GNU extension.
 .SH BUGS

man3/atan.3

@@ -71,16 +71,16 @@ that is the value whose tangent is
 On success, these functions return the principal value of the arc tangent of
 .IR x
 in radians; the return value is in the range [\-pi/2,\ pi/2].
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is +0 (\-0),
 +0 (\-0) is returned.
-
+.PP
 If
 .I x
 is positive infinity (negative infinity), +pi/2 (\-pi/2) is returned.
@@ -105,7 +105,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/atan2.3

@@ -69,31 +69,31 @@ the quadrant of the result.
 On success, these functions return the principal value of the arc tangent of
 .IR y/x
 in radians; the return value is in the range [\-pi,\ pi].
-
+.PP
 If
 .I y
 is +0 (\-0) and
 .I x
 is less than 0, +pi (\-pi) is returned.
-
+.PP
 If
 .I y
 is +0 (\-0) and
 .I x
 is greater than 0, +0 (\-0) is returned.
-
+.PP
 If
 .I y
 is less than 0 and
 .I x
 is +0 or \-0, \-pi/2 is returned.
-
+.PP
 If
 .I y
 is greater than 0 and
 .I x
 is +0 or \-0, pi/2 is returned.
-
+.PP
 .\" POSIX.1 says:
 .\" If
 .\" .I x
@@ -104,7 +104,7 @@ If either
 or
 .I y
 is NaN, a NaN is returned.
-
+.PP
 .\" POSIX.1 says:
 .\" If the result underflows, a range error may occur and
 .\" .I y/x
@@ -115,38 +115,38 @@ If
 is +0 (\-0) and
 .I x
 is \-0, +pi (\-pi) is returned.
-
+.PP
 If
 .I y
 is +0 (\-0) and
 .I x
 is +0, +0 (\-0) is returned.
-
+.PP
 If
 .I y
 is a finite value greater (less) than 0, and
 .I x
 is negative infinity, +pi (\-pi) is returned.
-
+.PP
 If
 .I y
 is a finite value greater (less) than 0, and
 .I x
 is positive infinity, +0 (\-0) is returned.
-
+.PP
 If
 .I y
 is positive infinity (negative infinity), and
 .I x
 is finite,
 pi/2 (\-pi/2) is returned.
-
+.PP
 If
 .I y
 is positive infinity (negative infinity) and
 .I x
 is negative infinity, +3*pi/4 (\-3*pi/4) is returned.
-
+.PP
 If
 .I y
 is positive infinity (negative infinity) and
@@ -175,7 +175,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/atanh.3

@@ -79,15 +79,15 @@ that is the value whose hyperbolic tangent is
 .SH RETURN VALUE
 On success, these functions return the inverse hyperbolic tangent of
 .IR x .
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is +0 (\-0), +0 (\-0) is returned.
-
+.PP
 If
 .I x
 is +1 or \-1,
@@ -98,7 +98,7 @@ and the functions return
 or
 .BR HUGE_VALL ,
 respectively, with the mathematically correct sign.
-
+.PP
 If the absolute value of
 .I x
 is greater than 1,
@@ -147,7 +147,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/atexit.3

@@ -51,7 +51,7 @@ or via return from the program's
 .IR main ().
 Functions so registered are called in
 the reverse order of their registration; no arguments are passed.
-
+.PP
 The same function may be registered multiple times:
 it is called once for each registration.
 .LP
@@ -86,7 +86,7 @@ T{
 .BR atexit ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD.
 .SH NOTES
@@ -96,14 +96,14 @@ Functions registered using
 .BR on_exit (3))
 are not called if a process terminates abnormally because
 of the delivery of a signal.
-
+.PP
 If one of the functions registered functions calls
 .BR _exit (2),
 then any remaining functions are not invoked,
 and the other process termination steps performed by
 .BR exit (3)
 are not performed.
-
+.PP
 POSIX.1 says that the result of calling
 .\" POSIX.1-2001, POSIX.1-2008
 .BR exit (3)
@@ -121,7 +121,7 @@ portable programs should not invoke
 .BR exit (3)
 inside a function registered using
 .BR atexit ().
-
+.PP
 The
 .BR atexit ()
 and
@@ -130,7 +130,7 @@ functions register functions on the same list:
 at normal process termination,
 the registered functions are invoked in reverse order
 of their registration by these two functions.
-
+.PP
 According to POSIX.1, the result is undefined if
 .BR longjmp (3)
 is used to terminate execution of one of the functions registered

man3/backtrace.3

@@ -75,7 +75,7 @@ to obtain the complete backtrace, make sure that
 and
 .I size
 are large enough.
-
+.PP
 Given the set of addresses returned by
 .BR backtrace ()
 in
@@ -100,7 +100,7 @@ by
 and must be freed by the caller.
 (The strings pointed to by the array of pointers
 need not and should not be freed.)
-
+.PP
 .BR backtrace_symbols_fd ()
 takes the same
 .I buffer
@@ -127,7 +127,7 @@ then the full backtrace was stored; if it is equal to
 .IR size ,
 then it may have been truncated, in which case the addresses of the
 oldest stack frames are not returned.
-
+.PP
 On success,
 .BR backtrace_symbols ()
 returns a pointer to the array

man3/basename.3

@@ -173,7 +173,7 @@ the POSIX versions of these functions modify the
 .I path
 argument, and segfault when called with a static string
 such as "/usr/".
-
+.PP
 Before glibc 2.2.1, the glibc version of
 .BR dirname ()
 did not correctly handle pathnames with trailing \(aq/\(aq characters,

man3/bindresvport.3

@@ -46,7 +46,7 @@ file descriptor
 to a privileged anonymous IP port,
 that is, a port number arbitrarily selected from the range 512 to 1023.
 .\" Glibc actually starts searching with a port # in the range 600 to 1023
-
+.PP
 If the
 .BR bind (2)
 performed by
@@ -56,7 +56,7 @@ is successful, and
 is not NULL, then
 .I sin\->sin_port
 returns the port number actually allocated.
-
+.PP
 .I sin
 can be NULL, in which case
 .I sin\->sin_family

man3/bsd_signal.3

@@ -54,7 +54,7 @@ The
 .BR bsd_signal ()
 function takes the same arguments, and performs the same task, as
 .BR signal (2).
-
+.PP
 The difference between the two is that
 .BR bsd_signal ()
 is guaranteed to provide reliable signal semantics, that is:
@@ -101,7 +101,7 @@ Use of
 should be avoided; use
 .BR sigaction (2)
 instead.
-
+.PP
 On modern Linux systems,
 .BR bsd_signal ()
 and
@@ -112,7 +112,7 @@ But on older systems,
 provided unreliable signal semantics; see
 .BR signal (2)
 for details.
-
+.PP
 The use of
 .I sighandler_t
 is a GNU extension;

man3/bsearch.3

@@ -86,7 +86,7 @@ T{
 .BR bsearch ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD.
 .SH EXAMPLE

man3/bswap.3

@@ -46,7 +46,7 @@ These macros are GNU extensions.
 The program below swaps the bytes of the 8-byte integer supplied as
 its command-line argument.
 The following shell session demonstrates the use of the program:
-
+.PP
 .nf
 .in +4n
 $ \fB./a.out 0x0123456789abcdef\fP

man3/btree.3

@@ -51,7 +51,7 @@ Since version 2.2, glibc no longer provides these interfaces.
 Probably, you are looking for the APIs provided by the
 .I libdb
 library instead.
-
+.PP
 The routine
 .BR dbopen (3)
 is the library interface to database files.
@@ -242,13 +242,13 @@ Only big and little endian byte order is supported.
 .BR hash (3),
 .BR mpool (3),
 .BR recno (3)
-
+.PP
 .IR "The Ubiquitous B-tree" ,
 Douglas Comer, ACM Comput. Surv. 11, 2 (June 1979), 121-138.
-
+.PP
 .IR "Prefix B-trees" ,
 Bayer and Unterauer, ACM Transactions on Database Systems, Vol. 2, 1
 (March 1977), 11-26.
-
+.PP
 .IR "The Art of Computer Programming Vol. 3: Sorting and Searching" ,
 D.E. Knuth, 1968, pp 471-480.

man3/byteorder.3

@@ -90,7 +90,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 POSIX.1-2001, POSIX.1-2008.
-
+.PP
 Some systems require the inclusion of
 .I <netinet/in.h>
 instead of

man3/bzero.3

@@ -43,7 +43,7 @@ function erases the data in the
 bytes of the memory starting at the location pointed to by
 .IR s ,
 by writing zeroes (bytes containing \(aq\\0\(aq) to that area.
-
+.PP
 The
 .BR explicit_bzero ()
 function performs the same task as
@@ -82,7 +82,7 @@ POSIX.1-2008 removes the specification of
 The
 .BR bzero ()
 function first appeared in 4.3BSD.
-
+.PP
 The
 .BR explicit_bzero ()
 function is a nonstandard extension that is also present on some of the BSDs.
@@ -110,7 +110,7 @@ by an incorrect or compromised program.
 Calls to
 .BR explicit_bzero ()
 are never optimized away by the compiler.
-
+.PP
 The
 .BR explicit_bzero ()
 function does not solve all problems associated with erasing sensitive data:
@@ -159,7 +159,7 @@ Indeed, it will make them worse, since, for example,
 it may force a variable that would otherwise have been optimized
 into a register to instead be maintained in (more vulnerable)
 RAM for its entire lifetime.
-
+.PP
 Notwithstanding the above details, for security-conscious applications, using
 .BR explicit_bzero ()
 is generally preferable to not using it.

man3/canonicalize_file_name.3

@@ -46,17 +46,17 @@ pathname components.
 Consecutive slash
 .RI ( / )
 characters are replaced by a single slash.
-
+.PP
 The returned string is dynamically allocated by
 .BR canonicalize_file_name ()
 and the caller should deallocate it with
 .BR free (3)
 when it is no longer required.
-
+.PP
 The call
 .I canonicalize_file_name(path)
 is equivalent to the call:
-
+.PP
     realpath(path, NULL);
 .SH RETURN VALUE
 On success,

man3/carg.3

@@ -21,14 +21,14 @@ Link with \fI\-lm\fP.
 These functions calculate the complex argument (also called phase angle) of
 .IR z ,
 with a branch cut along the negative real axis.
-
+.PP
 A complex number can be described by two real coordinates.
 One may use rectangular coordinates and gets
-
+.PP
 .nf
     z = x + I * y
 .fi
-
+.PP
 where
 .IR "x\ =\ creal(z)"
 and

man3/cbrt.3

@@ -74,7 +74,7 @@ representable real cube root.
 .SH RETURN VALUE
 These functions return the cube root of
 .IR x .
-
+.PP
 If
 .I x
 is +0, \-0, positive infinity, negative infinity, or NaN,

man3/ccos.3

@@ -20,7 +20,7 @@ Link with \fI\-lm\fP.
 .SH DESCRIPTION
 These functions calculate the complex cosine of
 .IR z .
-
+.PP
 The complex cosine function is defined as:
 .nf
 
@@ -42,7 +42,7 @@ T{
 .BR ccosl ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
 .SH SEE ALSO

man3/ccosh.3

@@ -20,7 +20,7 @@ Link with \fI\-lm\fP.
 .SH DESCRIPTION
 These functions calculate the complex hyperbolic cosine of
 .IR z .
-
+.PP
 The complex hyperbolic cosine function is defined as:
 .nf
 

man3/ceil.3

@@ -58,7 +58,7 @@ _ISOC99_SOURCE || _POSIX_C_SOURCE\ >=\ 200112L
 .SH DESCRIPTION
 These functions return the smallest integral value that is not less than
 .IR x .
-
+.PP
 For example,
 .IR ceil(0.5)
 is 1.0, and
@@ -67,7 +67,7 @@ is 0.0.
 .SH RETURN VALUE
 These functions return the ceiling of
 .IR x .
-
+.PP
 If
 .I x
 is integral, +0, \-0, NaN, or infinite,
@@ -92,7 +92,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to
@@ -113,7 +113,7 @@ of the exponent is smaller than the number of mantissa bits.
 For the IEEE-754 standard 32-bit and 64-bit floating-point numbers
 the maximum value of the exponent is 128 (respectively, 1024),
 and the number of mantissa bits is 24 (respectively, 53).)
-
+.PP
 The integral value returned by these functions may be too large
 to store in an integer type
 .RI ( int ,

man3/cexp.3

@@ -43,7 +43,7 @@ T{
 .BR cexpl ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
 .SH SEE ALSO

man3/clearenv.3

@@ -73,7 +73,7 @@ T{
 .BR clearenv ()
 T}	Thread safety	MT-Unsafe const:env
 .TE
-
+.sp 1
 .SH CONFORMING TO
 Various UNIX variants (DG/UX, HP-UX, QNX, ...).
 POSIX.9 (bindings for FORTRAN77).
@@ -98,7 +98,7 @@ is unavailable, the assignment
 
 .fi
 will probably do.
-
+.PP
 The
 .BR clearenv ()
 function may be useful in security-conscious applications that want to
@@ -107,14 +107,14 @@ executed using
 .BR exec (3).
 The application would do this by first clearing the environment
 and then adding select environment variables.
-
+.PP
 Note that the main effect of
 .BR clearenv ()
 is to adjust the value of the pointer
 .BR environ (7);
 this function does not erase the contents of the buffers
 containing the environment definitions.
-
+.PP
 The DG/UX and Tru64 man pages write: If
 .I environ
 has been modified by anything other than the

man3/clock.3

@@ -59,7 +59,7 @@ T{
 .BR clock ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 POSIX.1-2001, POSIX.1-2008, C89, C99.
 XSI requires that
@@ -96,7 +96,7 @@ The
 .BR times (2)
 function, which explicitly returns (separate) information about the
 caller and its children, may be preferable.
-
+.PP
 In glibc 2.17 and earlier,
 .BR clock ()
 was implemented on top of

man3/clog.3

@@ -21,7 +21,7 @@ Link with \fI\-lm\fP.
 These functions calculate the complex natural logarithm of
 .IR z ,
 with a branch cut along the negative real axis.
-
+.PP
 The logarithm
 .BR clog ()
 is the inverse function of the exponential

man3/clog10.3

@@ -23,18 +23,18 @@ Link with \fI\-lm\fP.
 The call
 .I clog10(z)
 is equivalent to:
-
+.PP
     clog(z)/log(10)
-
+.PP
 or equally:
-
+.PP
     log10(cabs(c)) + I * carg(c) / log(10)
-
+.PP
 The other functions perform the same task for
 .I float
 and
 .IR "long double" .
-
+.PP
 Note that
 .I z
 close to zero will cause an overflow.

man3/clog2.3

@@ -22,12 +22,12 @@ The call
 .I clog2(z)
 is equivalent to
 .IR clog(z)/log(2) .
-
+.PP
 The other functions perform the same task for
 .I float
 and
 .IR "long double" .
-
+.PP
 Note that
 .I z
 close to zero will cause an overflow.

man3/confstr.3

@@ -105,7 +105,7 @@ This value may be greater than
 which means that the value in
 .I buf
 is truncated.
-
+.PP
 If
 .I name
 is a valid configuration variable,

man3/copysign.3

@@ -64,7 +64,7 @@ These functions return a value whose absolute value matches that of
 .IR x ,
 but whose sign bit matches that of
 .IR y .
-
+.PP
 For example,
 .I "copysign(42.0,\ \-1.0)"
 and
@@ -75,7 +75,7 @@ On success, these functions return a value whose magnitude is taken from
 .I x
 and whose sign is taken from
 .IR y .
-
+.PP
 If
 .I x
 is a NaN,

man3/cos.3

@@ -71,11 +71,11 @@ given in radians.
 .SH RETURN VALUE
 On success, these functions return the cosine of
 .IR x .
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is positive infinity or negative infinity,
@@ -113,7 +113,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/cosh.3

@@ -74,20 +74,20 @@ which is defined mathematically as:
 .SH RETURN VALUE
 On success, these functions return the hyperbolic cosine of
 .IR x .
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is +0 or \-0, 1 is returned.
-
+.PP
 If
 .I x
 is positive infinity or negative infinity,
 positive infinity is returned.
-
+.PP
 If the result overflows,
 a range error occurs,
 and the functions return
@@ -127,7 +127,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/crypt.3

@@ -105,7 +105,7 @@ If you are planning on using the
 .BR crypt ()
 interface for a cryptography project, don't do it: get a good book on
 encryption and one of the widely available DES libraries.
-
+.PP
 .BR crypt_r ()
 is a reentrant version of
 .BR crypt ().
@@ -193,15 +193,15 @@ is a GNU extension.
 .SS Glibc notes
 The glibc2 version of this function supports additional
 encryption algorithms.
-
+.PP
 If
 .I salt
 is a character string starting with the characters "$\fIid\fP$"
 followed by a string terminated by "$":
 .RS
-
+.PP
 $\fIid\fP$\fIsalt\fP$\fIencrypted\fP
-
+.PP
 .RE
 then instead of using the DES machine,
 .I id
@@ -228,11 +228,11 @@ _
 6   | SHA-512 (since glibc 2.7)
 .TE
 .RE
-
+.PP
 So $5$\fIsalt\fP$\fIencrypted\fP is an SHA-256 encoded
 password and $6$\fIsalt\fP$\fIencrypted\fP is an
 SHA-512 encoded one.
-
+.PP
 "\fIsalt\fP" stands for the up to 16 characters
 following "$\fIid\fP$" in the salt.
 The encrypted part of the password string is the actual computed password.
@@ -243,7 +243,7 @@ MD5     | 22 characters
 SHA-256 | 43 characters
 SHA-512 | 86 characters
 .TE
-
+.sp 1
 The characters in "\fIsalt\fP" and "\fIencrypted\fP" are drawn from the set
 [\fBa\-zA\-Z0\-9./\fP].
 In the MD5 and SHA implementations the entire

man3/csin.3

@@ -20,7 +20,7 @@ Link with \fI\-lm\fP.
 .SH DESCRIPTION
 These functions calculate the complex sine of
 .IR z .
-
+.PP
 The complex sine function is defined as:
 .nf
 
@@ -42,7 +42,7 @@ T{
 .BR csinl ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
 .SH SEE ALSO

man3/csinh.3

@@ -20,7 +20,7 @@ Link with \fI\-lm\fP.
 .SH DESCRIPTION
 These functions calculate the complex hyperbolic sine of
 .IR z .
-
+.PP
 The complex hyperbolic sine function is defined as:
 .nf
 
@@ -42,7 +42,7 @@ T{
 .BR csinhl ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
 .SH SEE ALSO

man3/csqrt.3

@@ -40,7 +40,7 @@ T{
 .BR csqrtl ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
 .SH SEE ALSO

man3/ctan.3

@@ -20,7 +20,7 @@ Link with \fI\-lm\fP.
 .SH DESCRIPTION
 These functions calculate the complex tangent of
 .IR z .
-
+.PP
 The complex tangent function is defined as:
 .nf
 
@@ -42,7 +42,7 @@ T{
 .BR ctanl ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
 .SH SEE ALSO

man3/ctanh.3

@@ -20,7 +20,7 @@ Link with \fI\-lm\fP.
 .SH DESCRIPTION
 These functions calculate the complex hyperbolic tangent of
 .IR z .
-
+.PP
 The complex hyperbolic tangent function is defined
 mathematically as:
 .nf
@@ -43,7 +43,7 @@ T{
 .BR ctanhl ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
 .SH SEE ALSO

man3/ctime.3

@@ -246,7 +246,7 @@ and a negative value means that
 .BR mktime ()
 should (use timezone information and system databases to)
 attempt to determine whether DST is in effect at the specified time.
-
+.PP
 The
 .BR mktime ()
 function modifies the fields of the
@@ -266,7 +266,7 @@ Calling
 .BR mktime ()
 also sets the external variable \fItzname\fP with
 information about the current timezone.
-
+.PP
 If the specified broken-down
 time cannot be represented as calendar time (seconds since the Epoch),
 .BR mktime ()
@@ -281,33 +281,33 @@ and
 .BR localtime ()
 return a pointer to a
 .IR "struct\ tm" .
-
+.PP
 On success,
 .BR gmtime_r ()
 and
 .BR localtime_r ()
 return the address of the structure pointed to by
 .IR result .
-
+.PP
 On success,
 .BR asctime ()
 and
 .BR ctime ()
 return a pointer to a string.
-
+.PP
 On success,
 .BR asctime_r ()
 and
 .BR ctime_r ()
 return a pointer to the string pointed to by
 .IR buf .
-
+.PP
 On success,
 .BR mktime ()
 returns the calendar time (seconds since the Epoch),
 expressed as a value of type
 .IR time_t .
-
+.PP
 On error,
 .BR mktime ()
 returns the value
@@ -388,7 +388,7 @@ The thread-safe versions,
 and
 .BR localtime_r (),
 are specified by SUSv2.
-
+.PP
 POSIX.1-2001 says:
 "The
 .BR asctime (),
@@ -421,7 +421,7 @@ defined when
 was set before including
 .IR <time.h> .
 This is a BSD extension, present in 4.3BSD-Reno.
-
+.PP
 According to POSIX.1-2004,
 .BR localtime ()
 is required to behave as though

man3/dbopen.3

@@ -55,7 +55,7 @@ Since version 2.2, glibc no longer provides these interfaces.
 Probably, you are looking for the APIs provided by the
 .I libdb
 library instead.
-
+.PP
 .BR dbopen ()
 is the library interface to database files.
 The supported file formats are btree, hashed and UNIX file oriented.
@@ -556,6 +556,6 @@ locking, or transactions.
 .BR hash (3),
 .BR mpool (3),
 .BR recno (3)
-
+.PP
 .IR "LIBTP: Portable, Modular Transactions for UNIX" ,
 Margo Seltzer, Michael Olson, USENIX proceedings, Winter 1992.

man3/dl_iterate_phdr.3

@@ -41,7 +41,7 @@ The
 function allows an application to inquire at run time to find
 out which shared objects it has loaded,
 and the order in which they were loaded.
-
+.PP
 The
 .BR dl_iterate_phdr ()
 function walks through the list of an
@@ -51,7 +51,7 @@ once for each object,
 until either all shared objects have been processed or
 .I callback
 returns a nonzero value.
-
+.PP
 Each call to
 .I callback
 receives three arguments:
@@ -68,11 +68,11 @@ program as the second argument (also named
 .IR data )
 in the call to
 .BR dl_iterate_phdr ().
-
+.PP
 The
 .I info
 argument is a structure of the following type:
-
+.PP
 .in +4n
 .nf
 struct dl_phdr_info {
@@ -106,7 +106,7 @@ struct dl_phdr_info {
 };
 .fi
 .in
-
+.PP
 (The
 .IR ElfW ()
 macro definition turns its argument into the name of an ELF data
@@ -118,7 +118,7 @@ yields the data type name
 Further information on these types can be found in the
 .IR <elf.h> " and " <link.h>
 header files.)
-
+.PP
 The
 .I dlpi_addr
 field indicates the base address of the shared object
@@ -129,7 +129,7 @@ The
 .I dlpi_name
 field is a null-terminated string giving the pathname
 from which the shared object was loaded.
-
+.PP
 To understand the meaning of the
 .I dlpi_phdr
 and
@@ -144,7 +144,7 @@ shared object.
 The
 .I dlpi_phnum
 field indicates the size of this array.
-
+.PP
 These program headers are structures of the following form:
 .in +4n
 .nf
@@ -161,21 +161,21 @@ typedef struct {
 } Elf32_Phdr;
 .fi
 .in
-
+.PP
 Note that we can calculate the location of a particular program header,
 .IR x ,
 in virtual memory using the formula:
-
+.PP
 .nf
   addr == info\->dlpi_addr + info\->dlpi_phdr[x].p_vaddr;
 .fi
-
+.PP
 Possible values for
 .I p_type
 include the following (see
 .IR <elf.h>
 for further details):
-
+.PP
 .nf
 .in +4n
 #define PT_LOAD         1    /* Loadable program segment */
@@ -211,7 +211,7 @@ T{
 .BR dl_iterate_phdr ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 The
 .BR dl_iterate_phdr ()
@@ -234,7 +234,7 @@ structure; in that event, the
 .I size
 argument provides a mechanism for the callback function to discover
 whether it is running on a system with added fields.
-
+.PP
 The first object visited by
 .IR callback
 is the main program.
@@ -247,7 +247,7 @@ shared objects it has loaded.
 For each shared object, the program lists some information
 (virtual address, size, flags, and type)
 for each of the objects ELF segments.
-
+.PP
 The following shell session demonstrates the output
 produced by the program on an x86-64 system.
 The first shared object for which output is displayed
@@ -292,7 +292,7 @@ Name: "/lib64/ld-linux-x86-64.so.2" (7 segments)
      6: [0x7f55718afba0; memsz:    460] flags: 0x4; PT_GNU_RELRO
 .in
 .fi
-
+.PP
 .SS Program source
 \&
 .nf
@@ -352,6 +352,6 @@ main(int argc, char *argv[])
 .BR dlopen (3),
 .BR elf (5),
 .BR ld.so (8)
-
+.PP
 .IR "Executable and Linking Format Specification" ,
 available at various locations online.

man3/dladdr.3

@@ -75,7 +75,7 @@ could be found, then
 and
 .I dli_saddr
 are set to NULL.
-
+.PP
 The function
 .BR dladdr1 ()
 is like
@@ -97,7 +97,7 @@ structure (i.e.,
 defined in
 .I <link.h>
 as:
-
+.IP
 .in +4n
 .nf
 struct link_map {
@@ -134,7 +134,7 @@ yields the data type name
 which is defined in
 .IR <elf.h>
 as:
-
+.IP
 .in +4n
 .nf
 typedef struct  {
@@ -147,11 +147,11 @@ typedef struct  {
 } Elf64_Sym;
 .fi
 .in
-
+.IP
 The
 .I st_name
 field is an index into the string table.
-
+.IP
 The
 .I st_info
 field encodes the symbol's type and binding.
@@ -223,7 +223,7 @@ but not to a symbol in the shared object, then the
 and
 .I info->dli_saddr
 fields are set to NULL.
-
+.PP
 If the address specified in
 .I addr
 could not be matched to a shared object, then these functions return 0.

man3/dlerror.3

@@ -42,7 +42,7 @@ since the last call to
 The returned string does
 .I not
 include a trailing newline.
-
+.PP
 .BR dlerror ()
 returns NULL if no errors have occurred since initialization or since
 it was last called.

man3/dlinfo.3

@@ -54,7 +54,7 @@ The
 argument is a pointer to a buffer used to store information
 returned by the call; the type of this argument depends on
 .IR request .
-
+.PP
 The following values are supported for
 .IR request
 (with the corresponding type for
@@ -78,7 +78,7 @@ argument points to a pointer to a
 structure, defined in
 .I <link.h>
 as:
-
+.IP
 .in +4n
 .nf
 struct link_map {
@@ -154,7 +154,7 @@ to obtain the library search paths.
 The
 .I Dl_serinfo
 structure is defined as follows:
-
+.IP
 .in +4n
 .nf
 typedef struct {
@@ -171,7 +171,7 @@ typedef struct {
 Each of the
 .I dls_serpath
 elements in the above structure is a structure of the following form:
-
+.IP
 .in +4n
 .nf
 typedef struct {
@@ -182,7 +182,7 @@ typedef struct {
 } Dl_serpath;
 .fi
 .in
-
+.IP
 The
 .I dls_flags
 field is currently unused, and always contains zero.
@@ -250,7 +250,7 @@ and
 .B RTLD_DI_SERINFO
 requests to obtain the library search path list for the library.
 Here is an example of what we might see when running the program:
-
+.PP
 .in +4n
 .nf
 $ \fB./a.out /lib64/libm.so.6\fP

man3/dlopen.3

@@ -65,7 +65,7 @@ This handle is employed with other functions in the dlopen API, such as
 .BR dlinfo (3),
 and
 .BR dlclose ().
-
+.PP
 If
 .I filename
 .\" FIXME On Solaris, when handle is NULL, we seem to get back
@@ -242,7 +242,7 @@ and
 .I flags
 arguments, as well as the return value, are the same,
 except for the differences noted below.
-
+.PP
 The
 .BR dlmopen ()
 function differs from
@@ -261,7 +261,7 @@ call is made.)
 The
 .I Lmid_t
 type is an opaque handle that refers to a namespace.
-
+.PP
 The
 .I lmid
 argument is either the ID of an existing namespace
@@ -300,7 +300,7 @@ All shared objects that were automatically loaded when
 was invoked on the object referred to by
 .I handle
 are recursively closed in the same manner.
-
+.PP
 A successful return from
 .BR dlclose ()
 does not guarantee that the symbols associated with
@@ -322,11 +322,11 @@ On error
 (file could not be found, was not readable, had the wrong format,
 or caused errors during loading),
 these functions return NULL.
-
+.PP
 On success,
 .BR dlclose ()
 returns 0; on error, it returns a nonzero value.
-
+.PP
 Errors from these functions can be diagnosed using
 .BR dlerror (3).
 .SH VERSIONS
@@ -358,7 +358,7 @@ and
 The
 .BR dlmopen ()
 function is a GNU extension.
-
+.PP
 The
 .BR RTLD_NOLOAD ,
 .BR RTLD_NODELETE ,
@@ -375,7 +375,7 @@ dependent shared objects are implicitly loaded according to the usual rules,
 and symbol references are likewise resolved according to the usual rules,
 but such resolution is confined to the definitions provided by the
 objects that have been (explicitly and implicitly) loaded into the namespace.
-
+.PP
 The
 .BR dlmopen ()
 function permits object-load isolation\(emthe ability
@@ -395,7 +395,7 @@ without exposing those symbols to the entire application.
 This can be achieved by using a separate namespace and the
 .B RTLD_GLOBAL
 flag.
-
+.PP
 The
 .BR dlmopen ()
 function also can be used to provide better isolation than the
@@ -411,7 +411,7 @@ Thus,
 .BR RTLD_LOCAL
 is insufficient to isolate a loaded shared object except in the (uncommon)
 case where one has explicit control over all shared object dependencies.
-
+.PP
 Possible uses of
 .BR dlmopen ()
 are plugins where the author of the plugin-loading framework
@@ -426,7 +426,7 @@ Using
 .BR dlmopen (),
 this can be achieved by loading the same shared object file into
 different namespaces.
-
+.PP
 The glibc implementation supports a maximum of
 .\" DL_NNS
 16 namespaces.
@@ -450,7 +450,7 @@ See the
 info pages (under "Function attributes")
 .\" info gcc "C Extensions" "Function attributes"
 for further information.
-
+.PP
 An older method of (partially) achieving the same result is via the use of
 two special symbols recognized by the linker:
 .B _init
@@ -491,7 +491,7 @@ permit multiple initialization and finalization functions to be defined.
 .\" .\" void _init(void) __attribute__((constructor));
 .\" .\" void _fini(void) __attribute__((destructor));
 .\"
-
+.PP
 Since glibc 2.2.3,
 .BR atexit (3)
 can be used to register an exit handler that is automatically
@@ -519,7 +519,7 @@ looks up the address of the
 .BR cos (3)
 function, and prints the cosine of 2.0.
 The following is an example of building and running the program:
-
+.PP
 .in +4n
 .nf
 $ \fBcc dlopen_demo.c \-ldl\fP
@@ -594,5 +594,5 @@ main(void)
 .BR rtld-audit (7),
 .BR ld.so (8),
 .BR ldconfig (8)
-
+.PP
 gcc info pages, ld info pages

man3/dlsym.3

@@ -54,7 +54,7 @@ returns NULL.
 (The search performed by
 .BR dlsym ()
 is breadth first through the dependency tree of these shared objects.)
-
+.PP
 Since the value of the symbol could actually be NULL (so that a
 NULL return from
 .BR dlsym ()
@@ -103,7 +103,7 @@ and
 .B RTLD_NEXT
 from
 .IR <dlfcn.h> .
-
+.PP
 .PP
 The function
 .BR dlvsym ()

man3/drand48_r.3

@@ -87,7 +87,7 @@ These functions are the reentrant analogs of the functions described in
 Instead of modifying the global random generator state, they use
 the supplied data
 .IR buffer .
-
+.PP
 Before the first use, this struct must be initialized, for example,
 by filling it with zeros, or by calling one of the functions
 .BR srand48_r (),

man3/duplocale.3

@@ -54,7 +54,7 @@ The
 .BR duplocale ()
 function creates a duplicate of the locale object referred to by
 .IR locobj .
-
+.PP
 If
 .I locobj
 is
@@ -95,7 +95,7 @@ other functions that employ a locale handle, such as
 This is done by applying
 .BR duplocale ()
 to the value returned by the following call:
-
+.IP
     loc = uselocale((locale_t) 0);
 .IP
 This technique is necessary, because the above

man3/encrypt.3

@@ -142,7 +142,7 @@ T}	Thread safety	MT-Safe
 .BR encrypt (),
 .BR setkey ():
 POSIX.1-2001, POSIX.1-2008, SUS, SVr4.
-
+.PP
 The functions
 .BR encrypt_r ()
 and

man3/end.3

@@ -53,7 +53,7 @@ they are not standardized; use with caution.
 .SH NOTES
 The program must explicitly declare these symbols;
 they are not defined in any header file.
-
+.PP
 On some systems the names of these symbols are preceded by underscores,
 thus:
 .IR _etext ,
@@ -61,7 +61,7 @@ thus:
 and
 .IR _end .
 These symbols are also defined for programs compiled on Linux.
-
+.PP
 At the start of program execution,
 the program break will be somewhere near
 .IR &end

man3/endian.3

@@ -77,21 +77,21 @@ Feature Test Macro Requirements for glibc (see
 These functions convert the byte encoding of integer values from
 the byte order that the current CPU (the "host") uses,
 to and from little-endian and big-endian byte order.
-
+.PP
 The number,
 .IR nn ,
 in the name of each function indicates the size of
 integer handled by the function, either 16, 32, or 64 bits.
-
+.PP
 The functions with names of the form "htobe\fInn\fP" convert
 from host byte order to big-endian order.
-
+.PP
 The functions with names of the form "htole\fInn\fP" convert
 from host byte order to little-endian order.
-
+.PP
 The functions with names of the form "be\fInn\fPtoh" convert
 from big-endian order to host byte order.
-
+.PP
 The functions with names of the form "le\fInn\fPtoh" convert
 from little-endian order to host byte order.
 .SH VERSIONS
@@ -119,7 +119,7 @@ For example,
 .BR be32toh ()
 is identical to
 .BR ntohl ().
-
+.PP
 The advantage of the
 .BR byteorder (3)
 functions is that they are standard functions available

man3/envz_add.3

@@ -134,7 +134,7 @@ T{
 .BR envz_strip ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 These functions are a GNU extension.
 Handle with care.

man3/erf.3

@@ -77,20 +77,20 @@ defined as
 On success, these functions return the error function of
 .IR x ,
 a value in the range [\-1,\ 1].
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is +0 (\-0), +0 (\-0) is returned.
-
+.PP
 If
 .I x
 is positive infinity (negative infinity),
 +1 (\-1) is returned.
-
+.PP
 If
 .I x
 is subnormal,
@@ -132,7 +132,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/erfc.3

@@ -66,28 +66,28 @@ that is, 1.0 \- erf(x).
 On success, these functions return the complementary error function of
 .IR x ,
 a value in the range [0,2].
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is +0 or \-0, 1 is returned.
-
+.PP
 If
 .I x
 is positive infinity,
 +0 is returned.
-
+.PP
 If
 .I x
 is negative infinity,
 +2 is returned.
-
+.PP
 If the function result underflows and produces an unrepresentable value,
 the return value is 0.0.
-
+.PP
 If the function result underflows but produces a representable
 (i.e., subnormal) value,
 .\" e.g., erfc(27) on x86-32
@@ -129,7 +129,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/err.3

@@ -128,7 +128,7 @@ T{
 .BR vwarnx ()
 T}	Thread safety	MT-Safe locale
 .TE
-
+.sp 1
 .SH CONFORMING TO
 These functions are nonstandard BSD extensions.
 .\" .SH HISTORY

man3/errno.3

@@ -50,12 +50,12 @@ a function that succeeds
 .I is
 allowed to change
 .IR errno .
-
+.PP
 Valid error numbers are all nonzero;
 .I errno
 is never set to zero
 by any system call or library function.
-
+.PP
 For some system calls and library functions (e.g.,
 .BR getpriority (2)),
 \-1 is a valid return on success.
@@ -67,7 +67,7 @@ if the call returns a status that indicates that an error
 may have occurred, checking to see if
 .I errno
 has a nonzero value.
-
+.PP
 .I errno
 is defined by the ISO C standard to be a modifiable lvalue
 of type
@@ -78,14 +78,14 @@ may be a macro.
 .I errno
 is thread-local; setting it in one thread
 does not affect its value in any other thread.
-
+.PP
 All the error names specified by POSIX.1
 must have distinct values, with the exception of
 .B EAGAIN
 and
 .BR EWOULDBLOCK ,
 which may be the same.
-
+.PP
 .\" The following is now
 .\" POSIX.1 (2001 edition) lists the following symbolic error names.  Of
 .\" these, \fBEDOM\fP and \fBERANGE\fP are in the ISO C standard.  ISO C
@@ -208,7 +208,7 @@ Identifier removed (POSIX.1).
 .TP
 .B EILSEQ
 Invalid or incomplete multibyte or wide character (POSIX.1, C99).
-
+.IP
 The text shown here is the glibc error description;
 in POSIX.1, this error is described as "Illegal byte sequence".
 .TP
@@ -327,7 +327,7 @@ No such device (POSIX.1).
 .TP
 .B ENOENT
 No such file or directory (POSIX.1).
-
+.IP
 Typically, this error results when a specified pathname does not exist,
 or one of the components in the directory prefix of a pathname does not exist,
 or the specified pathname is a dangling symbolic link.

man3/error.3

@@ -61,7 +61,7 @@ should follow
 .I format
 in the argument list.
 The output is terminated by a newline character.
-
+.PP
 The program name printed by
 .BR error ()
 is the value of the global variable
@@ -72,13 +72,13 @@ initially has the same value as
 .IR argv[0] .
 The value of this variable can be modified to change the output of
 .BR error ().
-
+.PP
 If \fIstatus\fP has a nonzero value, then
 .BR error ()
 calls
 .BR exit (3)
 to terminate the program using the given value as the exit status.
-
+.PP
 The
 .BR error_at_line ()
 function is exactly the same as
@@ -98,20 +98,20 @@ The preprocessor values \fB__LINE__\fP and
 .BR error_at_line (),
 but other values can also be used.
 For example, these arguments could refer to a location in an input file.
-
+.PP
 If the global variable \fIerror_one_per_line\fP is set nonzero,
 a sequence of
 .BR error_at_line ()
 calls with the
 same value of \fIfilename\fP and \fIlinenum\fP will result in only
 one message (the first) being output.
-
+.PP
 The global variable \fIerror_message_count\fP counts the number of
 messages that have been output by
 .BR error ()
 and
 .BR error_at_line ().
-
+.PP
 If the global variable \fIerror_print_progname\fP
 is assigned the address of a function
 (i.e., is not NULL), then that function is called
@@ -137,7 +137,7 @@ MT-Unsafe\ race: error_at_line/error_one_per_line locale
 T}
 .TE
 .ad
-
+.PP
 The internal
 .I error_one_per_line
 variable is accessed (without any form of synchronization, but since it's an

man3/euidaccess.3

@@ -44,13 +44,13 @@ However, whereas
 performs checks using the real user and group identifiers of the process,
 .BR euidaccess ()
 uses the effective identifiers.
-
+.PP
 .I mode
 is a mask consisting of one or more of
 .BR R_OK ", " W_OK ", " X_OK ", and " F_OK ,
 with the same meanings as for
 .BR access (2).
-
+.PP
 .BR eaccess ()
 is a synonym for
 .BR euidaccess (),
@@ -96,7 +96,7 @@ performing some operation based on that information leads to race conditions:
 the file permissions may change between the two steps.
 Generally, it is safer just to attempt the desired operation and handle
 any permission error that occurs.
-
+.PP
 This function always dereferences symbolic links.
 If you need to check the permissions on a symbolic link, use
 .BR faccessat (2)

man3/exec.3

@@ -158,13 +158,13 @@ the current directory followed by the list of directories returned by
 (This
 .BR confstr (3)
 call typically returns the value "/bin:/usr/bin".)
-
+.PP
 If the specified filename includes a slash character, then
 .B PATH
 is ignored, and the file at the specified pathname is executed.
-
+.PP
 In addition, certain errors are treated specially.
-
+.PP
 If permission is denied for a file (the attempted
 .BR execve (2)
 failed with the error
@@ -175,7 +175,7 @@ they will return with
 .I errno
 set to
 .BR EACCES .
-
+.PP
 If the header of a file isn't recognized (the attempted
 .BR execve (2)
 failed with the error
@@ -221,7 +221,7 @@ T}	Thread safety	MT-Safe env
 .TE
 .SH CONFORMING TO
 POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The
 .BR execvpe ()
 function is a GNU extension.

man3/exp.3

@@ -70,26 +70,26 @@ logarithms) raised to the power of
 .SH RETURN VALUE
 On success, these functions return the exponential value of
 .IR x .
-
+.PP
 If
 .I x
 is a NaN,
 a NaN is returned.
-
+.PP
 If
 .I x
 is positive infinity,
 positive infinity is returned.
-
+.PP
 If
 .I x
 is negative infinity,
 +0 is returned.
-
+.PP
 If the result underflows,
 a range error occurs,
 and zero is returned.
-
+.PP
 If the result overflows,
 a range error occurs,
 and the functions return
@@ -103,7 +103,7 @@ See
 .BR math_error (7)
 for information on how to determine whether an error has occurred
 when calling these functions.
-
+.PP
 The following errors can occur:
 .TP
 Range error, overflow
@@ -137,7 +137,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/exp10.3

@@ -56,7 +56,7 @@ raised to the power of
 .SH RETURN VALUE
 On success, these functions return the base-10 exponential value of
 .IR x .
-
+.PP
 For various special cases, including the handling of infinity and NaN,
 as well as overflows and underflows, see
 .BR exp (3).
@@ -65,7 +65,7 @@ See
 .BR math_error (7)
 for information on how to determine whether an error has occurred
 when calling these functions.
-
+.PP
 For a discussion of the errors that can occur for these functions, see
 .BR exp (3).
 .SH VERSIONS

man3/exp2.3

@@ -68,7 +68,7 @@ These functions return the value of 2 raised to the power of
 .SH RETURN VALUE
 On success, these functions return the base-2 exponential value of
 .IR x .
-
+.PP
 For various special cases, including the handling of infinity and NaN,
 as well as overflows and underflows, see
 .BR exp (3).
@@ -77,7 +77,7 @@ See
 .BR math_error (7)
 for information on how to determine whether an error has occurred
 when calling these functions.
-
+.PP
 For a discussion of the errors that can occur for these functions, see
 .BR exp (3).
 .SH VERSIONS
@@ -98,7 +98,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/expm1.3

@@ -83,25 +83,25 @@ subtraction of two numbers that are nearly equal.
 .SH RETURN VALUE
 On success, these functions return
 .IR "exp(x)\ \-\ 1" .
-
+.PP
 If
 .I x
 is a NaN,
 a NaN is returned.
-
+.PP
 If
 .I x
 is +0 (\-0),
 +0 (\-0) is returned.
-
+.PP
 If
 .I x
 is positive infinity, positive infinity is returned.
-
+.PP
 If
 .I x
 is negative infinity, \-1 is returned.
-
+.PP
 If the result overflows, a range error occurs,
 and the functions return
 .RB - HUGE_VAL ,
@@ -153,7 +153,7 @@ values (where the function result approaches \-1),
 raises a bogus underflow floating-point exception.
 .\" FIXME .
 .\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6778
-
+.PP
 For some large positive
 .I x
 values,
@@ -164,7 +164,7 @@ overflow exception, and returns a NaN instead of positive infinity.
 .\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6814
 .\" e.g., expm1(1e5) through expm1(1.00199970127e5),
 .\" but not expm1(1.00199970128e5) and beyond.
-
+.PP
 Before version 2.11,
 .\" It looks like the fix was in 2.11, or possibly 2.12.
 .\" I have no test system for 2.11, but 2.12 passes.

man3/fabs.3

@@ -66,15 +66,15 @@ number
 .SH RETURN VALUE
 These functions return the absolute value of
 .IR x .
-
+.PP
 If
 .I x
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is \-0, +0 is returned.
-
+.PP
 If
 .I x
 is negative infinity or positive infinity, positive infinity is returned.
@@ -96,7 +96,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/fcloseall.3

@@ -40,7 +40,7 @@ Buffered output for each stream is written before it is closed
 (as for
 .BR fflush (3));
 buffered input is discarded.
-
+.PP
 The standard streams,
 .IR stdin ,
 .IR stdout ,

man3/fdim.3

@@ -37,13 +37,13 @@ These functions return the positive difference, max(\fIx\fP-\fIy\fP,0),
 between their arguments.
 .SH RETURN VALUE
 On success, these functions return the positive difference.
-
+.PP
 If
 .I x
 or
 .I y
 is a NaN, a NaN is returned.
-
+.PP
 If the result overflows,
 a range error occurs,
 and the functions return

man3/fenv.3

@@ -160,7 +160,7 @@ round to nearest (the default),
 round up (toward positive infinity),
 round down (toward negative infinity), and
 round toward zero.
-
+.PP
 Each of the macros
 .BR FE_TONEAREST ,
 .BR FE_UPWARD ,
@@ -179,7 +179,7 @@ The
 .BR fesetround ()
 function sets the rounding mode as specified by its argument
 and returns zero when it was successful.
-
+.PP
 C99 and POSIX.1-2008 specify an identifier,
 .BR FLT_ROUNDS ,
 defined in

man3/ferror.3

@@ -126,7 +126,7 @@ The functions
 and
 .BR ferror ()
 conform to C89, C99, POSIX.1-2001, and POSIX.1-2008.
-
+.PP
 The function
 .BR fileno ()
 conforms to POSIX.1-2001 and POSIX.1-2008.

man3/fexecve.3

@@ -103,7 +103,7 @@ T{
 .BR fexecve ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 POSIX.1-2008.
 This function is not specified in POSIX.1-2001,
@@ -121,7 +121,7 @@ needs to be mounted and available at the time of the call.
 .\" With the addition of the execveat(2), fexecve() can be implemented
 .\" even where /proc is unavailable. Review future glibc releases to
 .\" see if the implementation is changed to use execveat(2).
-
+.PP
 The idea behind
 .BR fexecve ()
 is to allow the caller to verify (checksum) the contents of
@@ -138,7 +138,7 @@ of a file could be changed between the checksumming and the call to
 .BR fexecve ();
 for that, the solution is to ensure that the permissions on the file
 prevent it from being modified by malicious users.
-
+.PP
 The natural idiom when using
 .BR fexecve ()
 is to set the close-on-exec flag on

man3/fflush.3

@@ -55,13 +55,13 @@ For output streams,
 forces a write of all user-space buffered data for the given output or update
 .I stream
 via the stream's underlying write function.
-
+.PP
 For input streams associated with seekable files
 (e.g., disk files, but not pipes or terminals),
 .BR fflush ()
 discards any buffered data that has been fetched from the underlying file,
 but has not been consumed by the application.
-
+.PP
 The open status of the stream is unaffected.
 .PP
 If the
@@ -109,7 +109,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C89, C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 POSIX.1-2001 did not specify the behavior for flushing of input streams,
 but the behavior is specified in POSIX.1-2008.
 .SH NOTES

man3/ffs.3

@@ -107,7 +107,7 @@ T}	Thread safety	MT-Safe
 .SH CONFORMING TO
 .BR ffs ():
 POSIX.1-2001, POSIX.1-2008, 4.3BSD.
-
+.PP
 The
 .BR ffsl ()
 and

man3/fgetc.3

@@ -138,10 +138,10 @@ T{
 .BR ungetc ()
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 POSIX.1-2001, POSIX.1-2008, C89, C99.
-
+.PP
 It is not advisable to mix calls to input functions from the
 .I stdio
 library with low-level calls to

man3/finite.3

@@ -99,7 +99,7 @@ functions return a nonzero value if
 .I x
 is neither infinite
 nor a "not-a-number" (NaN) value, and 0 otherwise.
-
+.PP
 The
 .BR isnan (),
 .BR isnanf (),
@@ -109,7 +109,7 @@ functions return a nonzero value if
 .I x
 is a NaN value,
 and 0 otherwise.
-
+.PP
 The
 .BR isinf (),
 .BR isinff (),

man3/floor.3

@@ -57,7 +57,7 @@ _ISOC99_SOURCE || _POSIX_C_SOURCE\ >=\ 200112L
 .SH DESCRIPTION
 These functions return the largest integral value that is not greater than
 .IR x .
-
+.PP
 For example,
 .IR floor(0.5)
 is 0.0, and
@@ -66,7 +66,7 @@ is \-1.0.
 .SH RETURN VALUE
 These functions return the floor of
 .IR x .
-
+.PP
 If
 .I x
 is integral, +0, \-0, NaN, or an infinity,
@@ -91,7 +91,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/fma.3

@@ -48,13 +48,13 @@ current rounding mode (see
 These functions return the value of
 .IR x " * " y " + " z ,
 rounded as one ternary operation.
-
+.PP
 If
 .I x
 or
 .I y
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 times
@@ -64,7 +64,7 @@ is an exact infinity, and
 is an infinity with the opposite sign,
 a domain error occurs,
 and a NaN is returned.
-
+.PP
 .\" POSIX.1-2008 allows some possible differences for the following two
 .\" domain error cases, but on Linux they are treated the same (AFAICS).
 .\" Nevertheless, we'll mirror POSIX.1 and describe the two cases
@@ -80,7 +80,7 @@ a domain error occurs, and
 a NaN is returned.
 .\" POSIX.1 says that a NaN or an implementation-defined value shall
 .\" be returned for this case.
-
+.PP
 If one of
 .I x
 or
@@ -91,7 +91,7 @@ is a NaN,
 .\" POSIX.1 makes the domain error optional for this case.
 a domain error occurs, and
 a NaN is returned.
-
+.PP
 If
 .I x
 times
@@ -100,11 +100,11 @@ is not an infinity times zero (or vice versa), and
 .I z
 is a NaN,
 a NaN is returned.
-
+.PP
 If the result overflows,
 a range error occurs, and
 an infinity with the correct sign is returned.
-
+.PP
 If the result underflows,
 a range error occurs, and
 a signed 0 is returned.

man3/fmax.3

@@ -43,9 +43,9 @@ These functions return the maximum of
 .I x
 and
 .IR y .
-
+.PP
 If one argument is a NaN, the other argument is returned.
-
+.PP
 If both arguments are NaN, a NaN is returned.
 .SH ERRORS
 No errors occur.

man3/fmemopen.3

@@ -40,7 +40,7 @@ function opens a stream that permits the access specified by
 The stream allows I/O to be performed on the string or memory buffer
 pointed to by
 .IR buf .
-
+.PP
 The
 .I mode
 argument specifies the semantics of I/O on the stream,
@@ -113,7 +113,7 @@ buffer
 .I size
 counts that byte)
 to allow for this.
-
+.PP
 In a stream opened for reading,
 null bytes (\(aq\\0\(aq) in the buffer do not cause read
 operations to return an end-of-file indication.
@@ -121,11 +121,11 @@ A read from the buffer will indicate end-of-file
 only when the current buffer position advances
 .I size
 bytes past the start of the buffer.
-
+.PP
 Write operations take place either at the current position
 (for modes other than append), or at the current size of the stream
 (for append modes).
-
+.PP
 Attempts to write more than
 .I size
 bytes to the buffer result in an error.
@@ -135,7 +135,7 @@ By default, such errors will be visible
 buffer is flushed.
 Disabling buffering with the following call
 may be useful to detect errors at the time of an output operation:
-
+.PP
     setbuf(stream, NULL);
 .SH RETURN VALUE
 Upon successful completion,
@@ -161,12 +161,12 @@ T{
 .BR fmemopen (),
 T}	Thread safety	MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 POSIX.1-2008.
 This function is not specified in POSIX.1-2001,
 and is not widely available on other systems.
-
+.PP
 POSIX.1-2008 specifies that \(aqb\(aq in
 .IR mode
 shall be ignored.
@@ -180,7 +180,7 @@ returned by this function
 (i.e.,
 .BR fileno (3)
 will return an error if called on the returned stream).
-
+.PP
 With version 2.22, binary mode (see below) was removed,
 many longstanding bugs in the implementation of
 .BR fmemopen ()
@@ -199,7 +199,7 @@ writes don't implicitly add a terminating null byte, and
 is relative to the end of the buffer (i.e., the value specified by the
 .I size
 argument), rather than the current string length.
-
+.PP
 An API bug afflicted the implementation of binary mode:
 to specify binary mode, the \(aqb\(aq must be the
 .I second
@@ -211,7 +211,7 @@ This is inconsistent with the treatment of
 .IR mode
 by
 .BR fopen (3).
-
+.PP
 Binary mode was removed in glibc 2.22; a \(aqb\(aq specified in
 .I mode
 has no effect.
@@ -226,7 +226,7 @@ fails with the error
 It would be more consistent if this case successfully created
 a stream that then returned end-of-file on the first attempt at reading;
 since version 2.22, the glibc implementation provides that behavior.
-
+.PP
 In versions of glibc before 2.22,
 specifying append mode ("a" or "a+") for
 .BR fmemopen ()
@@ -236,7 +236,7 @@ sets the initial buffer position to the first null byte, but
 the end of the stream)
 does not force subsequent writes to append at the end of the stream.
 This bug is fixed in glibc 2.22.
-
+.PP
 In versions of glibc before 2.22, if the
 .I mode
 argument to
@@ -253,7 +253,7 @@ However, in this case the glibc
 .BR fmemopen ()
 sets the buffer position to \-1.
 This bug is fixed in glibc 2.22.
-
+.PP
 In versions of glibc before 2.22,
 .\" https://sourceware.org/bugzilla/show_bug.cgi?id=14292
 when a call to
@@ -270,7 +270,7 @@ was
 .IR subtracted
 from the end-of-stream position, instead of being added.
 This bug is fixed in glibc 2.22.
-
+.PP
 The glibc 2.9 addition of "binary" mode for
 .BR fmemopen ()
 .\" http://sourceware.org/bugzilla/show_bug.cgi?id=6544

man3/fmin.3

@@ -43,9 +43,9 @@ These functions return the minimum of
 .I x
 and
 .IR y .
-
+.PP
 If one argument is a NaN, the other argument is returned.
-
+.PP
 If both arguments are NaN, a NaN is returned.
 .SH ERRORS
 No errors occur.

man3/fmod.3

@@ -89,25 +89,25 @@ such that the returned value has the same sign as
 .I x
 and a magnitude less than the magnitude of
 .IR y .
-
+.PP
 If
 .I x
 or
 .I y
 is a NaN, a NaN is returned.
-
+.PP
 If
 .I x
 is an infinity,
 a domain error occurs, and
 a NaN is returned.
-
+.PP
 If
 .I y
 is zero,
 a domain error occurs, and
 a NaN is returned.
-
+.PP
 If
 .I x
 is +0 (\-0), and
@@ -155,7 +155,7 @@ T}	Thread safety	MT-Safe
 .TE
 .SH CONFORMING TO
 C99, POSIX.1-2001, POSIX.1-2008.
-
+.PP
 The variant returning
 .I double
 also conforms to

man3/fmtmsg.3

@@ -243,7 +243,7 @@ Before glibc 2.16, the
 .BR fmtmsg ()
 function uses a static variable that is not protected,
 so it is not thread-safe.
-
+.PP
 Since glibc 2.16,
 .\" Modified in commit 7724defcf8873116fe4efab256596861eef21a94
 the
@@ -259,7 +259,7 @@ and environment variables
 and
 .B SEV_LEVEL
 come from System V.
-
+.PP
 The function
 .BR fmtmsg ()
 and the environment variable

man3/fopen.3

@@ -202,7 +202,7 @@ The
 argument is used just as in the
 .BR fopen ()
 function.
-
+.PP
 If the
 .I pathname
 argument is a null pointer,
@@ -213,7 +213,7 @@ that is,
 .BR freopen ()
 reopens the pathname that is associated with the stream.
 The specification for this behavior was added in the C99 standard, which says:
-
+.PP
 .RS
 In this case,
 the file descriptor associated with the stream need not be closed
@@ -303,7 +303,7 @@ T}	Thread safety	MT-Safe
 .BR fopen (),
 .BR freopen ():
 POSIX.1-2001, POSIX.1-2008, C89, C99.
-
+.PP
 .BR fdopen ():
 POSIX.1-2001, POSIX.1-2008.
 .SH NOTES
@@ -364,9 +364,9 @@ and
 support the following syntax
 in
 .IR mode :
-
+.PP
 .BI "    ,ccs=" string
-
+.PP
 The given
 .I string
 is taken as the name of a coded character set and