From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 102453 invoked by alias); 3 Nov 2016 18:32:17 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 102438 invoked by uid 89); 3 Nov 2016 18:32:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:1615 X-HELO: mail-vk0-f52.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=C7JHpOemqwuPDifPk1Tez2tTfbGxWFUmpdBypTiC5Ss=; b=AGJYhgWwAt+pYYBzIYMsaQp+ibLOwZEdTjTCs9C5/fxYwOM305JMwXHyrWCOimUTvy KlZmxkvTl6YLssM5wwcgmcPaI7iuGoHlW4f+LTlyznnR5Mta6KyHPZYJpBIQB15vJv9P xpfeAwLjz2Kje93EPKhPL83xCtKlWC/L0Gn0XjUOQcR/juLSgxD9Zb4LJvL9haJil9et qP3LJrWxXwOC7TcbOBqalIBF+wKC8/hnYZeyzhzqHU8gi4+tE+C1fFacjGAvOti5CLQa D+ejgLwpXHf19oWEmY+NhdsRWwUM25iUhC3o6sktyfTmWNSbDriLls8tUfUIJR8Yhe1e FFfQ== X-Gm-Message-State: ABUngvcBoWyA+jlrEpn3C1G92q1T1MHD+kSDHU680d5yn7IV4NkSNivdi89LB3jbBO24R44k X-Received: by 10.31.102.6 with SMTP id a6mr8596273vkc.175.1478197924604; Thu, 03 Nov 2016 11:32:04 -0700 (PDT) Subject: Re: sysdeps/unix/sysv/linux directory structure question To: libc-alpha@sourceware.org References: <1478195265.4630.6.camel@caviumnetworks.com> <1478196741.4630.10.camel@caviumnetworks.com> From: Adhemerval Zanella Message-ID: <8c9e7acd-c6be-159a-4036-de3554aa04b5@linaro.org> Date: Thu, 03 Nov 2016 18:32:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <1478196741.4630.10.camel@caviumnetworks.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-11/txt/msg00112.txt.bz2 On 03/11/2016 16:12, Steve Ellcey wrote: > 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? Yes, my understanding is 'sysdeps/generics' is glibc defined internal semantics, where the linux/generic means the kernel abi (recall that glibc still supports non-linux targets).