This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] Make _FILE_OFFSET_BITS=64 default.
- From: Paul Eggert <eggert at cs dot ucla dot edu>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Wed, 05 Mar 2014 11:04:18 -0800
- Subject: Re: [RFC] Make _FILE_OFFSET_BITS=64 default.
- Authentication-results: sourceware.org; auth=none
- References: <1393521776-1102-1-git-send-email-reprofy at etersoft dot ru> <530F79C1 dot 2040508 at cs dot ucla dot edu> <20140305091331 dot GA6031 at domone dot podge> <5316FF9F dot 1060301 at redhat dot com> <20140305180704 dot GM184 at brightrain dot aerifal dot cx> <53176EEE dot 8070500 at redhat dot com>
On 03/05/2014 10:37 AM, Florian Weimer wrote:
Doesn't it changes the definition of off_t and ino_t as well? While
these aren't supposed to be used in public header files, such a change
seems fairly risky to me.
Why so? Can you give an example of a realistic risk that might happen
in a typical application? The examples I can think of are either so
contrived that they wouldn't be worth worrying about in practice, or
they're already a problem and changing the default _FILE_OFFSET_BITS
wouldn't make things significantly worse. For example, an application
that blindly copies an off_t value to an int variable is already busted
on 64-bit platforms when files are large, even without the change.