From: Joseph Myers <joseph@codesourcery.com>
To: Steve Ellcey <sellcey@caviumnetworks.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: sysdeps/unix/sysv/linux directory structure question
Date: Thu, 03 Nov 2016 18:01:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611031758360.2232@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1478195265.4630.6.camel@caviumnetworks.com>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On Thu, 3 Nov 2016, Steve Ellcey wrote:
> 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-
generic is for newer architectures using the generic syscall ABI, where
syscalls that can be implemented in terms of newer syscalls are generally
omitted (so only statat syscalls not the older stat ones, for example),
and where structures are the same between different architectures as far
as possible (whereas various structures on older architectures commonly
tried to follow the layout used by some proprietary Unix on that
architecture).
> bit kernels?  Is that why it has a wordsize-32 subdirectory?  Are
The generic syscall ABI only has 64-bit versions of various structures,
with 32-bit architectures expected to do EOVERFLOW handling in userspace.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-11-03 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 17:48 Steve Ellcey
2016-11-03 18:01 ` Joseph Myers [this message]
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=alpine.DEB.2.20.1611031758360.2232@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=sellcey@caviumnetworks.com \
/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).