From: Steve Ellcey <sellcey@caviumnetworks.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: sysdeps/unix/sysv/linux directory structure question
Date: Thu, 03 Nov 2016 18:12:00 -0000 [thread overview]
Message-ID: <1478196741.4630.10.camel@caviumnetworks.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611031758360.2232@digraph.polyomino.org.uk>
On Thu, 2016-11-03 at 18:01 +0000, Joseph Myers wrote:
> 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.
So this use of 'generic' is different than the 'sysdeps/generic'
directory. Â I.e. sysdeps/generics is automatically added to the end of
the sysdep directory search list, but 'sysdeps/unix/sysv/linux/generic'
is only going to be used if it appears in a targets Implies file. Â Is
that correct?
Steve Ellcey
sellcey@caviumnetworks.com
next prev parent reply other threads:[~2016-11-03 18:12 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
2016-11-03 18:12 ` Steve Ellcey [this message]
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=1478196741.4630.10.camel@caviumnetworks.com \
--to=sellcey@caviumnetworks.com \
--cc=joseph@codesourcery.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).