search for: __ieee_big_endian

...in the LLVM distribution, that is, a compiler that would identify the target as LLVM and produce byte code by default. There was very little to do in terms of porting. Basically the only thing I needed to tweak in the source code was to define floating point endiness, which I randomly picked to be __IEEE_BIG_ENDIAN. Hopefully someone can confirm or correct my choice. The next task is to go for the system calls. As I said earlier, I plan to use intrinsic functions as place holders. Any opinions how to name them? Currently there are a few intrinsics that have to do with libc, like llvm.memcpy and llvm.memmove....

I have been browsing through the newlib documentation at <http://sources.redhat.com/newlib/> and pondering about how newlib relates to LLVM. Comments welcome, again. As I see it, there are basically two parts of libc that need to be considered. Much of libc is stuff like atoi(), isalpha(), etc. which are just convenience routines written in ANSI C. For these, it should be sufficient to

We are going to use LLVM in a compiler project for transport triggered processors. See Wikipedia for more on transport triggering: <http://en.wikipedia.org/wiki/Transport_Triggered_Architectures>. One thing we need is some sort of libc. We are targeting embedded systems, and I have been looking at things like newlib. Are there people out there doing something similar? Or any advice or

...is, a compiler that would identify the target as > LLVM and produce byte code by default. > > There was very little to do in terms of porting. Basically > the only thing I needed to tweak in the source code was to define > floating point endiness, which I randomly picked to be > __IEEE_BIG_ENDIAN. Hopefully someone can confirm or correct my > choice. I would think that it would follow the endianness of the host platform, but someone else might have a more definitive answer. > > The next task is to go for the system calls. As I said earlier, > I plan to use intrinsic functions...