J. Mayer wrote:
Following my previous message, I did a patch that makes syscalls take
target_long/target_ulong argument and return target_long value instead
of long/unsigned long.
I also included the #ifdef protection for do_socketcall and do_ipc to
avoid compilation warnings.
And I also
On Wed, 2007-09-19 at 10:07 +0100, Thiemo Seufer wrote:
J. Mayer wrote:
Following my previous message, I did a patch that makes syscalls take
target_long/target_ulong argument and return target_long value instead
of long/unsigned long.
I also included the #ifdef protection for
-devel] RFC: linux user problems
Date: Mon, 17 Sep 2007 23:04:00 +0200
It seems to me that there are many problems in linux-user/syscall.c
- minor fixes, just to avoid compilation warnings:
do_socketcall should be inside a #ifdef TARGET_NR_socketcall block
do_ipc should be inside a #ifdef
It seems to me that there are many problems in linux-user/syscall.c
- minor fixes, just to avoid compilation warnings:
do_socketcall should be inside a #ifdef TARGET_NR_socketcall block
do_ipc should be inside a #ifdef TARGET_NR_ipc block
- problems for 64 bits targets:
it seems that do_syscall
On Monday 17 September 2007, J. Mayer wrote:
It seems to me that there are many problems in linux-user/syscall.c
- problems for 64 bits targets:
it seems that do_syscall and child functions should take target_long /
target_ulong arguments instead of long / unsigned long. This would make
a
On Mon, 2007-09-17 at 23:10 +0100, Paul Brook wrote:
On Monday 17 September 2007, J. Mayer wrote:
It seems to me that there are many problems in linux-user/syscall.c
- problems for 64 bits targets:
it seems that do_syscall and child functions should take target_long /
target_ulong
