I just tried foo.c on up-to-date arm-sid and armel-sid systems, both under qemu and on real hardware and I cannot reproduce the problem; all succeed the same way, for example:
[EMAIL PROTECTED]:~$ /usr/bin/gcc-4.2 foo.c [EMAIL PROTECTED]:~$ ./a.out 0xbe92ec84 0x1 0x2 0x3 [EMAIL PROTECTED]:~$ gcc --version gcc (GCC) 4.2.3 20071123 (prerelease) (Debian 4.2.2-4) So I can only suspect a leisner problem of some kind. If you would like to try reproducing the problem here, please get in touch and I'll arrange access. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
