C integrated RPC
Joel Sherrill
joel.sherrill@oarcorp.com
Wed Jan 21 18:47:00 GMT 2009
andrew babanin wrote:
>> 2009/1/21 Ian Lance Taylor <iant@google.com>:
>>
>
>> You say it needs only libc, but of course it needs
>> more than the ISO C library functions. Is the code written in a way
>> that makes it easy to port to other systems?
>>
>
> CRPC has two main parts - C-wrapper compiler and shared library.
> Compiler is implicitly written with libc functions and standart Unix
> system calls.
> At this point it can be ported to any platform, that supports C.
> Wrapper compiler is built on my own parser, it does not need Lex/Bison.
> Parser partially implemets C syntax - variable declarations, typedefs and
> function prototype declarations.
> Library is dependent only on libc whether there is no need in threading support.
>
> The system should work on any BSD-like system, I have tested on
> Darwin(Power-PC),
> and it was ok. Also system will work on 32-bit and 64-bit systems
> (tested on amd64).
> On Linux everything is ok. Port it on CygWin is not a big problem to.
>
I think this would have been useful on at least one project
in my history. :)
Ian mentioned embedded systems in an earlier question
and I am still unsure what you require of the OS in terms
of services to work. Cygwin is very close to a "real UNIX"
from a programming viewpoint.
+ What do you require of the threading support?
+ Network services?
+ filesystem?
+ etc
RTEMS is a single process, multithreaded RTOS with
a port of the FreeBSD TCP/IP stack. Do you think that
would that be sufficient to run on?
Have you build this cross yet?
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
More information about the Gcc
mailing list