Re: syscall macro fails upon compilation

2007-07-06 Thread H. Peter Anvin
Andi Kleen wrote: >> They were *always* broken for 64-bit arguments on 32-bit machines, however. > > Well syscall() doesn't support that at all (unless you split by hand) > On i386 it just happens to work, because the calling convention is equivalent. On some other 32-bit platforms it works tha

Re: syscall macro fails upon compilation

2007-07-06 Thread Andi Kleen
> They were *always* broken for 64-bit arguments on 32-bit machines, however. Well syscall() doesn't support that at all (unless you split by hand) -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at

Re: syscall macro fails upon compilation

2007-07-06 Thread H. Peter Anvin
Gautam Singaraju wrote: > I am surprised that syscalls have been removed. Anyway, I plan to > write a device node with read and write functions just so that I can > call a method from a user space. What are my other choices? man syscall -hpa - To unsubscribe from this list: send the line

Re: syscall macro fails upon compilation

2007-07-06 Thread H. Peter Anvin
Andi Kleen wrote: > "H. Peter Anvin" <[EMAIL PROTECTED]> writes: > >> Gautam Singaraju wrote: >>> I use the _syscall0 macro. >> Don't. The _syscall*() macros have been unsupported for ages, > > That's not true. I supported them on x86 before they were removed against > my objections. > >> and b

Re: syscall macro fails upon compilation

2007-07-06 Thread Gautam Singaraju
I am surprised that syscalls have been removed. Anyway, I plan to write a device node with read and write functions just so that I can call a method from a user space. What are my other choices? -- Gautam On 06 Jul 2007 13:53:41 +0200, Andi Kleen <[EMAIL PROTECTED]> wrote: "H. Peter Anvin" <[EMA

Re: syscall macro fails upon compilation

2007-07-06 Thread Andi Kleen
"H. Peter Anvin" <[EMAIL PROTECTED]> writes: > Gautam Singaraju wrote: > > I use the _syscall0 macro. > > Don't. The _syscall*() macros have been unsupported for ages, That's not true. I supported them on x86 before they were removed against my objections. > and broken for ever longer. Well,

Re: syscall macro fails upon compilation

2007-07-05 Thread Davide Libenzi
On Thu, 5 Jul 2007, Gautam Singaraju wrote: > I have been adding a syscall to the kernel (v 2.6.21); I am able to > compile and boot into the kernel. However, the userspace macro fails > to compile with the following message: "error: expected declaration > specifiers or â...â before âmycallâ". I c

Re: syscall macro fails upon compilation

2007-07-05 Thread H. Peter Anvin
Gautam Singaraju wrote: > I use the _syscall0 macro. Don't. The _syscall*() macros have been unsupported for ages, and broken for ever longer. -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info