search for: ching1119

On 10 March 2010 16:57, 琬菁楊 <ching1119.cs96 at g2.nctu.edu.tw> wrote: > I think the main issue is that EFI C dialect is not ANSI-C compliant: the > size of pointer is determined at the run-time and therefore the layout of > the structure is not static. Does LLVM support this model? Hi Ching, The LLVM IR doesn't care ab...

Hello all, I am highly interestd in implementing C compiler for EFI Byte Code in LLVM and participate in Google Summer Code. EFI is a much larger, more complex,OS-like replacement for the older BIOS firmware interface present in all IBM PC-compatible personal computers. and the EFI specification provides for a processor-independent device driver environment(like virtualmachine), called EFI Byte

On Mon, Mar 15, 2010 at 10:50 AM, Renato Golin <rengolin at systemcall.org> wrote: > On 10 March 2010 16:57, 琬菁楊 <ching1119.cs96 at g2.nctu.edu.tw> wrote: >> I think the main issue is that EFI C dialect is not ANSI-C compliant: the >> size of pointer is determined at the run-time and therefore the layout of >> the structure is not static. Does LLVM support this model? > > Hi Ching, > > T...

Hi Tristan, > But it is not an error, otherwise it would be hard to use malloc() like > functions. > > I cannot understand that it would be hard to use malloc() like functions the parameter passed to malloc is evaluated at runtime what is the issue of malloc when sizeof is determined at runtime? thanks ching -------------- next part -------------- An HTML attachment was scrubbed...

Hello Chris, Which won't matter (as long as sizeof is consistent), because EFI is a > closed system. > What is the meaning of closed system?? Is it 1. not open source 2. EBC binary is only running on a single EFI EBC interpreter and never interfacing with the outside VM?? thanks ching -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello everyone, I want to do a LLVM server which is multi-thread, translating independent LLVM IR files per thread in parallel. I am curious about the status of multi-thread LLVM. Any replies is appreciated. Ching -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120703/133299ec/attachment.html>

Hello, Chris > 2010/3/20 Chris Lattner <clattner at apple.com> > > >> On Mar 19, 2010, at 2:40 PM, Louis Gerbarg wrote: >> >> >>> What do you mean by "variable sized pointers"? What does: >>> >>> struct S {void *X; }; >>> >>> return for sizeof(struct S); ? >>> >> >> It doesn't, at

2010/3/20 Louis Gerbarg <lgerbarg at gmail.com> > On Fri, Mar 19, 2010 at 3:47 PM, Chris Lattner <clattner at apple.com> wrote: > >> >> On Mar 19, 2010, at 11:08 AM, 琬菁楊 wrote: >> >> >> Hello Tristan and all, >> >> I have already know that if I want to do this feature(c -> EFI Byte code) >> for GCC >> I should further

Hello Tristan and all, I have already know that if I want to do this feature(c -> EFI Byte code) for GCC I should further modify the GCC front end(parser) to solve the problem (the size of pointer is determined at run time). I have read a powerpoint about LLVM ( http://llvm.org/pubs/2008-10-04-ACAT-LLVM-Intro.pdf) It is the LLVM-GCC design graph (

Hello Chris, I have survey the efi specification and ask some question to efi engineer. Difference between EFI C and ANSI C is as following: 1. void* In EFI C, the void* is 4-byte for 32-bit processor and 8-byte for 64-bit processor. And it can appears in any where like ANSI C. So the main problem is that struct layout like struct S{ void* X; }; is not static. 2.