From: Paul Eggert <eggert@cs.ucla.edu>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: x32 and width of blksize_t, suseconds_t
Date: Fri, 16 Mar 2012 01:19:18 -0700 [thread overview]
Message-ID: <4F62F786.2070907@cs.ucla.edu> (raw)
In-Reply-To: <4F62F152.1040909@cs.ucla.edu>
Come to think of it, the proposed x32 patch may have issues
with blksize_t and suseconds_t as well. POSIX says that an x32
implementation must support at least one programming environment
(presumably settable via a feature test macro) where blksize_t
and suseconds_t are no wider than 'long'; see
<http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_types.h.html>.
But if I understand things correctly, x32 glibc would
define these to be 'long long'. This issue affects system
calls such as 'stat' and 'select'.
next prev parent reply other threads:[~2012-03-16 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120315192515.GA6585@intel.com>
[not found] ` <20120315195000.7E3BE2C0A3@topped-with-meat.com>
[not found] ` <CAMe9rOpXRcO6a4cFEU=s1Gjzzt87zvyzuLhAWupc2pOX6az6ig@mail.gmail.com>
[not found] ` <4F625570.7050003@cs.ucla.edu>
[not found] ` <CAMe9rOpvnhPmpmsLedmOjjYB9SghZiov-cOUi+wrYvKaP+c9pQ@mail.gmail.com>
[not found] ` <4F6267B1.3090805@cs.ucla.edu>
2012-03-15 22:19 ` PATCH [3/n]: Add __snseconds_t and __SNSECONDS_T_TYPE H.J. Lu
2012-03-16 7:52 ` Paul Eggert
2012-03-16 8:19 ` Paul Eggert [this message]
2012-03-16 14:31 ` x32 and width of blksize_t, suseconds_t H. Peter Anvin
2012-03-16 14:45 ` Joseph S. Myers
2012-03-16 16:14 ` H.J. Lu
2012-03-16 15:49 ` PATCH [3/n]: Add __snseconds_t and __SNSECONDS_T_TYPE H.J. Lu
2012-03-16 18:54 ` Paul Eggert
2012-03-16 19:16 ` H.J. Lu
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=4F62F786.2070907@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.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