Displaying 3 results from an estimated 3 matches for "4e5ea081".
2010 Mar 19
0
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
...gt; GCC front end??
What do you mean by "variable sized pointers"? What does:
struct S {void *X; };
return for sizeof(struct S); ?
-Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100319/4e5ea081/attachment.html>
2010 Mar 19
1
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
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 (
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