On 2014-04-22, Peter Bigot <big...@acm.org> wrote:
> I expect there'll be some issues with newlib as well; it appears to
> use a unique syscall interface that I haven't tried to reverse
> engineer.
I don't understand. A "syscall" API is usually the interface between
libc code (which is running in user mode) and an underlying OS kernel
that's running in protected mode. Into what What OS kernel is newlib
expecting to be able to make syscalls?
For example, the syscall interface I deal with is the API between
either glibc or uclibc and the Linux kernel. It's architecture
specific, since the the mechanism for swithcing to/from protected mode
usually has to be done in assembler. It's typically something like:
* Load parameters in to specific registers
* Execute some variety of "SWI" instruction to generate a hardware
exception/interrupt.
--
Grant Edwards grant.b.edwards Yow! Actually, what I'd
at like is a little toy
gmail.com spaceship!!
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
