Re: System calls parameter restrictions
- From: "David Schwartz" <davids@xxxxxxxxxxxxx>
- Date: 28 Oct 2006 05:03:19 -0700
phil-news-nospam@xxxxxxxx wrote:
Structs small enough to fit in available register space could be passed
in much the same way many archtectures do pass values. It's just a big
complex value. What if you were passing a 64 bit integer by value, on a
32 bit machine, knowing that there is really no true value as cuh, but
only a joining of a pair of 32 bit integers? It really doesn't matter.
It can be dealt with one way or another. It can be loaded into a register
or a copy can be made through use of pass by reference (pointer). It's
just a matter of how the kernel syscall interface is designed and to the
extent such a design depends on it, the ABI.
But that would mean that changing a structure would break the ABI. That
doesn't sound like it's worth it. Think about structures of unknown
length, such as 'struct sockaddr'. (How do you tell the compiler a
structure has unknown length?)
DS
.
- Follow-Ups:
- Re: System calls parameter restrictions
- From: phil-news-nospam
- Re: System calls parameter restrictions
- References:
- System calls parameter restrictions
- From: Rafael Almeida
- Re: System calls parameter restrictions
- From: David Schwartz
- Re: System calls parameter restrictions
- From: Rafael Almeida
- Re: System calls parameter restrictions
- From: David Schwartz
- Re: System calls parameter restrictions
- From: phil-news-nospam
- System calls parameter restrictions
- Prev by Date: Two nodes under /dev/EEPROM/ for one EEPROM
- Next by Date: how to probe an i/o access
- Previous by thread: Re: System calls parameter restrictions
- Next by thread: Re: System calls parameter restrictions
- Index(es):
Relevant Pages
|