From: Steve Ellcey <sellcey@caviumnetworks.com>
To: <libc-alpha@sourceware.org>
Subject: sysdeps/unix/sysv/linux directory structure question
Date: Thu, 03 Nov 2016 17:48:00 -0000 [thread overview]
Message-ID: <1478195265.4630.6.camel@caviumnetworks.com> (raw)
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.
Steve Ellcey
sellcey@caviumnetworks.com
next reply other threads:[~2016-11-03 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 17:48 Steve Ellcey [this message]
2016-11-03 18:01 ` Joseph Myers
2016-11-03 18:12 ` Steve Ellcey
2016-11-03 18:32 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1478195265.4630.6.camel@caviumnetworks.com \
--to=sellcey@caviumnetworks.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).