Displaying 3 results from an estimated 3 matches for "index16".
Did you mean:
index1
2009 Aug 30
0
[LLVMdev] Strange error in generated assembly
...uot;tart.core.Array[tart.core.String]"*
%s, i32 %i14) ; <%tart.core.String*> [#uses=3]
%src.data = getelementptr %tart.core.String* %get15, i32 0, i32 4 ; <[0 x
i8]*> [#uses=1]
%result.data = getelementptr %tart.core.String* %alloc, i32 0, i32 4 ; <[0
x i8]*> [#uses=1]
%index16 = load i32* %index ; <i32> [#uses=1]
%src.length = getelementptr %tart.core.String* %get15, i32 0, i32 1 ;
<i32*> [#uses=1]
%length17 = load i32* %src.length ; <i32> [#uses=1]
%4 = sext i32 %length17 to i64 ; <i64> [#u...
2010 Mar 19
0
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
> How does EFI describe structures if the pointer size can change? This
> shouldn't be a harder problem than C struct -> llvm struct. I assume
> the EFI bytecode has some way to describe them. What is it?
EFI describe structures almost like C.
There are EBC instructions that have two immediates: one for 32bits pointers and one for 64bits pointers.
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