search for: b95030

Displaying 5 results from an estimated 5 matches for "b95030".

2010 Mar 19
1
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
...> 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 ( http://www.im.ntu.edu.tw/~b95030/llvm_gcc.png<http://www.im.ntu.edu.tw/%7Eb95030/llvm_gcc.png> ). According to the above discussion , LLVM IR doesn't care about the size of pointers. I am wondering how could LLVM support dynamic pointer size model without modifying GCC front end?? thanks ching -------------- next part...
2010 Mar 19
0
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
...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 (http://www.im.ntu.edu.tw/~b95030/llvm_gcc.png). > According to the above discussion , LLVM IR doesn't care about the size of pointers. > I am wondering how could LLVM support dynamic pointer size model without modifying > GCC front end?? What do you mean by "variable sized pointers"? What does: struct S...
2010 Mar 19
4
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
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
2010 Mar 19
5
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
...ld 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 ( > http://www.im.ntu.edu.tw/~b95030/llvm_gcc.png<http://www.im.ntu.edu.tw/%7Eb95030/llvm_gcc.png> > ). > According to the above discussion , LLVM IR doesn't care about the size of > pointers. > I am wondering how could LLVM support dynamic pointer size model without > modifying > GCC front end?? > >...
2010 Mar 30
0
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
...ont 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 ( >> http://www.im.ntu.edu.tw/~b95030/llvm_gcc.png<http://www.im.ntu.edu.tw/%7Eb95030/llvm_gcc.png> >> ). >> According to the above discussion , LLVM IR doesn't care about the size of >> pointers. >> I am wondering how could LLVM support dynamic pointer size model without >> modifying >> GC...