From: Alistair Francis <alistair23@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Alistair Francis <alistair.francis@wdc.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2 2/2] Define __STATFS_MATCHES_STATFS64
Date: Wed, 25 Sep 2019 15:53:31 -0700 [thread overview]
Message-ID: <CAKmqyKNRRKb6UMWzsEqCJqDdWpa0uQ+7HSQwWVCPiCPGGN8Ysw@mail.gmail.com> (raw)
In-Reply-To: <mvmef04ddvc.fsf@suse.de>
On Wed, Sep 25, 2019 at 12:38 AM Andreas Schwab <schwab@suse.de> wrote:
>
> On Sep 24 2019, Alistair Francis <alistair.francis@wdc.com> wrote:
>
> > * sysdeps/unix/sysv/linux/generic/bits/statfs.h: Define
> > __STATFS_MATCHES_STATFS64 to handle 64-bit __fsblkcnt_t
> > and t__fsfilcnt_t types on 32-bit hosts.
>
> The patch doesn't do that though. It uses it, but doesn't define it.
There are currently no 32-bit hosts with 64-bit time_t in glibc. This
patch is in preparation of the RV32 series/other y2038 safe archs.
Alistair
>
> Andreas.
>
> --
> Andreas Schwab, SUSE Labs, schwab@suse.de
> GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
> "And now for something completely different."
next prev parent reply other threads:[~2019-09-25 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 0:31 [PATCH v2 1/2] sysdeps/stat: Handle 64-bit ino_t types on 32-bit hosts Alistair Francis
2019-09-25 0:31 ` [PATCH v2 2/2] Define __STATFS_MATCHES_STATFS64 Alistair Francis
2019-09-25 7:38 ` Andreas Schwab
2019-09-25 22:53 ` Alistair Francis [this message]
2019-09-25 7:39 ` [PATCH v2 1/2] sysdeps/stat: Handle 64-bit ino_t types on 32-bit hosts Andreas Schwab
2019-09-25 22:52 ` Alistair Francis
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKmqyKNRRKb6UMWzsEqCJqDdWpa0uQ+7HSQwWVCPiCPGGN8Ysw@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).