Displaying 3 results from an estimated 3 matches for "4bc5cd10".
2010 Dec 22
0
[LLVMdev] Why IR portable?
Hello
> We all know LLVM IR is portable, but it uses ILP32
No, it doesn't use this.
> It seems it already assigned their sizes mapping with types.
> How can it be portable? Isn't it been written there?
Everything depends on how you generated the IR.
You might find this link
http://llvm.org/docs/FAQ.html#platformindependent useful.
--
With best regards, Anton Korobeynikov
2010 Dec 22
2
[LLVMdev] Why IR portable?
...h best regards, Anton Korobeynikov
> Faculty of Mathematics and Mechanics, Saint Petersburg State University
>
--
Best regards,
Wen-Han (Nowar)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101222/4bc5cd10/attachment.html>
2010 Dec 22
4
[LLVMdev] Why IR portable?
Dear all,
I cannot find the answer of this question.
We all know LLVM IR is portable, but it uses ILP32 and record the target
layout within the IR.
target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64
:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64"
target triple = "x86_64-linux-gnu"
It seems it already assigned