From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <1663922.YALRc7vFOO@coil> References: <3E93FE94-76BC-4B38-9FB2-DEDC5C3CEF9E@quintile.net> <1663922.YALRc7vFOO@coil> Date: Mon, 7 May 2012 11:16:00 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=0015175cba308b3b1504bf6f8ef5 Subject: Re: [9fans] integer width on AMD64 (was: Re: AMD64 system) Topicbox-Message-UUID: 85327228-ead7-11e9-9d60-3106f5b1d025 --0015175cba308b3b1504bf6f8ef5 Content-Type: text/plain; charset=UTF-8 uintptr for pointer/integer (uintptr_t in ANSI_t "t for type" style). the problem with large file offset doesn't exist in Plan 9, because the type of seek changed, instead of Unix's messing about trying to conserve the type of lseek (because it's got an "l" in it, I suppose), or worse, on some systems making it dependent on a series of #defines and weak pragmas to select lseek64 vs lseek32. honestly. change the type of off_t and be done with it. as Plan 9 did, you can change the system call number to allow old executables to work for seek/stat/fstat and so on when the file offset changes. put another way, why shouldn't executables running in 32 bit mode be able to access large files? that's therefore independent of the physical rep. of "long". On 7 May 2012 11:01, dexen deVries wrote: > when i asked about int and long size on amd64, i was more concerned with > ability to cast between pointer and integer and handling offset of large > files. > --0015175cba308b3b1504bf6f8ef5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable uintptr for pointer/integer (uintptr_t in ANSI_t "t for type" sty= le).
the problem with large file offset doesn't exist in Plan 9, be= cause the type
of seek changed, instead of Unix's messing abo= ut trying to conserve the type
of lseek (because it's got an "l" in it, I suppose), or = worse, on some systems making
it dependent on a series of #define= s and weak pragmas to select lseek64 vs lseek32.
honestly. change= the type of off_t and be done with it. as Plan 9 did, you can change
the system call number to allow old executables to work for seek/stat/= fstat and so on
when the file offset changes. put another way, wh= y shouldn't executables running
in 32 bit mode be able to acc= ess large files? that's therefore independent of the physical rep. of &= quot;long".

On 7 May 2012 11:01, dexen deVries <d= exen.devries@gmail.com> wrote:
when i asked about int and long size on amd64, i was more = concerned with
ability to cast between pointer and integer and handling offset of large fi= les.

--0015175cba308b3b1504bf6f8ef5--