This is the mail archive of the newlib@sources.redhat.com mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Syscall

To: Prasad Venkata Boddupalli <bprasad at CS dot Arizona dot EDU>
Subject: Re: Syscall
From: Philip Blundell <philb at gnu dot org>
Date: Sat, 02 Jun 2001 11:04:45 +0100
Cc: newlib <newlib at sources dot redhat dot com>
References: <Pine.GSO.4.33.0106011854310.15105-100000@lectura.CS.Arizona.EDU>

>syscode is always 0x23456, no matter what system call I use in my C
>program. I see from the arch/arm/kernel/entry-common.S, that the syscall
>code is retrieved using the link register. I was confused a bit by this
>inconsistency. The above cross-compiler (arm-elf-gcc) uses the newlib.
>That made me wonder if glibc and newlib differ in the way they store
>the syscall codes and if the numbers used for syscalls differ between
>them.

Newlib simply doesn't support the Linux/ARM ABI.

p.

PGP signature

Follow-Ups:
- Re: Syscall
  - From: Aaron J. Grier

References:
- Re: Syscall
  - From: Prasad Venkata Boddupalli

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]