Messages in this thread | | | Date | Tue, 30 Aug 2011 10:56:37 +0100 | From | Alan Cox <> | Subject | Re: RFD: x32 ABI system call numbers |
| |
> > The only programs which really care are those which map many gigs > > of stuff into memory (IE: big databases, etc). > > You mean anything that mmaps a file? > 2-3GB is not a whole lot these days.
For most stuff its a lot, and most apps that mmap files mmap the bits they need. O_LARGEFILE and 64bit time_t do make sense though.
> 2Gb is a very similar thing as Linus y2038, just you're much more > likely to hit it.
Also if using a 64bit time_t means less compat gunge it makes things much easier. At that point 32bit time_t becomes a userspace/library thunking problen.
> IMHO the only excuse right now for 32bit is to use it in a JIT > that can dynamically expand the pointer. Or for old binaries.
Or for a lot of code which runs way faster in 32bit pointer mode. Less memory, smaller cache footprint.
Alan
| |