search for: llva_syscall

I managed to compile newlib with llvm-gcc yesterday. That is, the machine independent part is now basically done, and the syscall part contains no-op stubs provided by libgloss. I haven't tested the port yet, but since newlib has already been ported to many architectures, I would be pretty surprised if there were any major problems. A couple of things I noticed when configuring newlib for

...s of intrinsics that we would add to LLVM to support an operating system. In our implementation, we wrote them all as external library functions. While I suspect that most of our paper is not relevant in solving the problems you're working on, some bits of information (like ioread/iowrite and llva_syscall) may be of interest to you. If you read about something in the LLVA-OS paper and have questions on it, please feel free to ask. The paper is rather light on details because we had an incredibly short page limit. So, llva_ioread() and llva_iowrite() read and write values to I/O locations. The lo...

John Criswell kirjoitti: > So, let me see if I understand this right: > > First, it sounds like you're programming on the bare processor, so your > I/O instructions are either special processor instructions or volatile > loads/stores to special memory locations. Yes. In more detail, instruction words directly control the data transports inside the processor, and I/O is