This is the mail archive of the
mailing list for the glibc project.
sysdeps/unix/sysv/linux directory structure question
- From: Steve Ellcey <sellcey at caviumnetworks dot com>
- To: <libc-alpha at sourceware dot org>
- Date: Thu, 3 Nov 2016 10:47:45 -0700
- Subject: sysdeps/unix/sysv/linux directory structure question
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Steve dot Ellcey at cavium dot com;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
I am looking at some of the consolidation patches that Yury Norov and
Adhemerval Zanella have submitted and I was wondering if anyone could
help clarify the structure of sysdeps/unix/sysv/linux for me.
Basically we have some functions defined directly in this directory and
there is also a wordsize-64 directory, presumably for <name>64 versions
of those functions.
But there is also a generic directory and some files (send.c) are
defined in the linux directory and in the linux/generic
directory. Also the generic directory has a wordsize-32 subdirectory
(but not a wordsize-64 one).
So I have several questions. What is the difference between
sysdeps/unix/sysv/linux and sysdeps/unix/sysv/linux/generic and why
are some files in one vs. the other vs. both? Is generic only for 64-
bit kernels? Is that why it has a wordsize-32 subdirectory? Are
functions transitioning (or supposed to be transitioning) from one
directory to another?
I did look at the hierarchy convention in the glibc manual (D.2.1
Layout of the sysdeps Directory Hierarchy) but that did not help
me with these questions.