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

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: HAndling Syscalls

From: Yves Rutschle <y dot rutschle at indigovision dot com>
To: savithri venkatachalapathy <venkasav at ece dot orst dot edu>
Cc: crossgcc at sources dot redhat dot com
Date: Wed, 10 Jul 2002 20:21:24 +0100
Subject: Re: HAndling Syscalls
References: <Pine.GHP.4.31.0207101011090.11777-100000@pal.ECE.ORST.EDU>

On Wed, Jul 10, 2002 at 10:18:52AM -0700, savithri venkatachalapathy wrote:
> And I have some doubts about how compilers handle syscalls.

Usually system calls would not actually depend on the
compiler. They are rather implemented by the C library.
Hence, when your program calls printf(), that enters the
C library which eventually will perform a write system call.

(In fact, you may even have a system without an operating
system, in which case you wouldn't get any system call at
all: printf() would call into the library which would
eventually call some hardware-dependent function that would
send stuff to the UART directly.)

The details will depend on the library you use...

/Y


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

References:
- HAndling Syscalls
  - From: savithri venkatachalapathy

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