From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Carlos O'Donell <carlos@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
<libc-ports@sourceware.org>
Subject: Re: [RFC] Copy as much as you can during a 32-bit stat before returning EOVERFLOW?
Date: Tue, 26 Feb 2013 22:59:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1302262252590.339@digraph.polyomino.org.uk> (raw)
In-Reply-To: <512D1CF4.4080607@cs.ucla.edu>
On Tue, 26 Feb 2013, Paul Eggert wrote:
> Here's a different idea: enable wide ino_t, time_t, etc. if
> _FILE_OFFSET_BITS is 64. This would require zero changes to
ino_t is already __ino64_t when _FILE_OFFSET_BITS is 64 (ignoring the lack
of 64-bit ino_t in the kernel stat64 interface on SH). 64-bit time_t
interfaces on 32-bit systems will require major new work in both glibc and
the Linux kernel (including new versions of various syscalls, though
presumably only the relevant syscalls that are in the generic ABI and not
the legacy ones).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-02-26 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 19:55 Carlos O'Donell
2013-02-26 20:37 ` Paul Eggert
2013-02-26 22:59 ` Joseph S. Myers [this message]
2013-02-26 21:00 ` Roland McGrath
2013-02-26 23:05 ` Joseph S. Myers
2013-02-27 19:26 ` Carlos O'Donell
2013-02-26 23:49 ` Rich Felker
2013-02-26 23:58 ` Roland McGrath
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=Pine.LNX.4.64.1302262252590.339@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@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).