summaryrefslogtreecommitdiff
path: root/gnu/lib/libiberty/src/fdmatch.c
diff options
context:
space:
mode:
Diffstat (limited to 'gnu/lib/libiberty/src/fdmatch.c')
-rw-r--r--gnu/lib/libiberty/src/fdmatch.c32
1 files changed, 13 insertions, 19 deletions
diff --git a/gnu/lib/libiberty/src/fdmatch.c b/gnu/lib/libiberty/src/fdmatch.c
index 7af039f5a2b..979c214d5d4 100644
--- a/gnu/lib/libiberty/src/fdmatch.c
+++ b/gnu/lib/libiberty/src/fdmatch.c
@@ -20,25 +20,19 @@ Boston, MA 02111-1307, USA. */
/*
-NAME
-
- fdmatch -- see if two file descriptors refer to same file
-
-SYNOPSIS
-
- int fdmatch (int fd1, int fd2)
-
-DESCRIPTION
-
- Check to see if two open file descriptors refer to the same file.
- This is useful, for example, when we have an open file descriptor
- for an unnamed file, and the name of a file that we believe to
- correspond to that fd. This can happen when we are exec'd with
- an already open file (stdout for example) or from the SVR4 /proc
- calls that return open file descriptors for mapped address spaces.
- All we have to do is open the file by name and check the two file
- descriptors for a match, which is done by comparing major&minor
- device numbers and inode numbers.
+@deftypefn Extension int fdmatch (int @var{fd1}, int @var{fd2})
+
+Check to see if two open file descriptors refer to the same file.
+This is useful, for example, when we have an open file descriptor for
+an unnamed file, and the name of a file that we believe to correspond
+to that fd. This can happen when we are exec'd with an already open
+file (@code{stdout} for example) or from the SVR4 @file{/proc} calls
+that return open file descriptors for mapped address spaces. All we
+have to do is open the file by name and check the two file descriptors
+for a match, which is done by comparing major and minor device numbers
+and inode numbers.
+
+@end deftypefn
BUGS