3 ms·
It seems bit odd that they are so proud of 64-bit time_t that they even made their release song about that, with this sentence in the description: > In the sam
by zokier 13y ago
It seems bit odd that they are so proud of 64-bit time_t that they even made their release song about that, with this sentence in the description:
> In the same way, the road is paved for the 64-bit time_t transition. Other operating systems can now make this jump
Haven't Linux and FreeBSD been on 64bit time_t for like 10 years now?
- edwintorok 13y agoIf you install a 32-bit Linux, then time_t is still 32-bit, only on 64-bit Linux you get 64-bit time_t. Although by 2038 I hope we won't have many 32-bit systems around...
- bananas 13y agoEmbedded devices are likely to be 32-bit for a very long time yet. I'd consider 100+ years to be a reasonable number! 64-bit devices are much more complicated (bus size, peripherals, part count) and therefore more expensive. If your entire task fits in a 32-bit space there is little motivation to use a 64-bit core.
- zokier 13y ago> 64-bit devices are much more complicated (bus size, peripherals, part count) and therefore more expensive I don't see why 64 bit core would imply any additional external complexity? Didn't 68k have 32bit core and work just fine down to 8bit external bus?
- bananas 13y agoIt won't on full SoC devices but most ARM embedded devices of that sort have all sorts of peripherals which are bus connected so the bus will need to be external.
- mrweasel 13y agoI think one of the points from OpenBSD is that 32 bit systems will be around. Legacy system are one thing, but how about embedded systems. Manufacturers will want to use 32bit processors in new system for a long long time, simply because they can save a few cents.
- Sanddancer 13y agoIf it ain't broke...There are still 8 bit and 16 bit cores being produced today. Hoping products will become obsolete is one of the big reasons y2k was a problem.
- throwaway2048 13y agonot on 32 bit systems, which is what that part of the release announcement is about. All unix 64bit systems have a 64bit time_t, only OpenBSD and NetBSD at this point have 64bit time_t on 32 bit systems. This cannot be changed on Linux without breaking userland ABI/API compatibility, something which the maintainers refuse to do.
- zokier 13y agooh, 32 bit systems, I do remember those good old beige boxes :) yeah, I know, those silly ARM chips have been bit on the slow side getting on the 64bit train.
- legulere 13y agoExcept x32 systems, as that issue had to be tackled before integration into the linux kernel.
- zokier 13y agoBut x32 doesn't work on 32-bit systems
- bch 13y agoI can't speak for Linux/FreeBSD, but NetBSD has been 64-bit time_t (all ports)[0] since 6.0, which was Oct 2012[1]. [0] https://www.netbsd.org/releases/formal-6/NetBSD-6.0.html https://www.netbsd.org/releases/formal-6/NetBSD-6.0.html [1] https://www.netbsd.org/about/history.html https://www.netbsd.org/about/history.html