This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: p{read,write}{,64} mips n64 changes
On Mar 20, 2003, Andreas Jaeger <aj at suse dot de> wrote:
> __LONG_LONG_PAIR ((type) ((var) >> 32), \
> (type) ((var) & 0xffffffff))
> Is this not feasible?
The `>> 32' and truncation with `& 0xffffffff' is only used in the
off64_t versions (pread64 and pwrite64), but not in the off_t versions
(pread and pwrite). In fact, shifting by 32 would invoke undefined
behavior in the off_t versions, so we'd have to make it two shifts
instead.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva at {redhat dot com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva at {lsd dot ic dot unicamp dot br, gnu.org}
Free Software Evangelist Professional serial bug killer
- References:
- p{read,write}{,64} mips n64 changes
- Re: p{read,write}{,64} mips n64 changes
- Re: p{read,write}{,64} mips n64 changes
- Re: p{read,write}{,64} mips n64 changes
- Re: p{read,write}{,64} mips n64 changes
- Re: p{read,write}{,64} mips n64 changes
- Re: p{read,write}{,64} mips n64 changes
- Re: p{read,write}{,64} mips n64 changes