From: Cyril Hrubis <chrubis@suse.cz>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Christoph Hellwig <hch@lst.de>, Jeff Layton <jlayton@redhat.com>,
linux-fsdevel@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [Linux PATCH] fcntl: add new F_OFD_*32 constants and handle them appropriately
Date: Thu, 25 Aug 2016 14:05:46 +0200 [thread overview]
Message-ID: <20160825120546.GG10490@rei.lan> (raw)
In-Reply-To: <87bn0ht68r.fsf@mid.deneb.enyo.de>
Hi!
> > Yes, that's what glibc folks should do for now given that they still
> > seem to refuse being draggred into the present.
>
> Your assumptions are wrong, at least for some (many?) of us. 32-bit
> architectures are legacy; giving them a 64-bit off_t (or even time_t)
> does not really change that. A hard ABI transition is simply not
> worth the effort.
Unfortunately there are still 32bit processors manufactured and sold
even these days, mainly for IOT though.
For instance Intel has released Quark (32bit i586 400Mhz CPU used in
Edison board) in 2014. First two batches of Raspberry Pi were 32bit
ARMv6/ARMv7, these are still sold today, etc.
So I would say that 32bit will stick with us for another ten years at
least.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2016-08-25 12:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 12:03 [Linux PATCH] fcntl: add new F_OFD_*32 constants and handle them appropriately Jeff Layton
2016-08-18 13:24 ` Cyril Hrubis
2016-08-18 13:54 ` Jeff Layton
2016-08-18 14:06 ` Cyril Hrubis
2016-08-18 17:05 ` Christoph Hellwig
2016-08-18 17:28 ` Jeff Layton
2016-08-18 17:31 ` Christoph Hellwig
2016-08-18 17:46 ` Mike Frysinger
2016-08-18 17:52 ` Christoph Hellwig
2016-08-18 18:16 ` Mike Frysinger
2016-08-18 19:01 ` Zack Weinberg
2016-08-18 19:36 ` Paul Eggert
2016-08-19 13:20 ` Zack Weinberg
2016-08-19 15:02 ` Joseph Myers
2016-08-19 15:45 ` Zack Weinberg
2016-08-19 16:58 ` Joseph Myers
2016-08-19 19:50 ` Zack Weinberg
2016-08-18 20:52 ` Joseph Myers
2016-08-25 11:53 ` Florian Weimer
2016-08-25 12:05 ` Cyril Hrubis [this message]
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=20160825120546.GG10490@rei.lan \
--to=chrubis@suse.cz \
--cc=fw@deneb.enyo.de \
--cc=hch@lst.de \
--cc=jlayton@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).