Displaying 7 results from an estimated 7 matches for "mduleid".
Did you mean:
moduleid
2011 Sep 15
2
[LLVMdev] problem with sgt's on Sparc machine
Hi guys,
Thanks for the input. However, it seems that the code still produces the
wrong output on a Sparc machine.
My current llvm_print.bc code is:
--------------------------------------------------------------------------------------------------
; MduleID = '<stdin>'
target datalayout =
"e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-n32"
target triple = "sparc-unknown-linux"
@P = global i32 1
@dP = global i32 1
@.str = private constant [4 x i8] c"%d\0A\00", align...
2011 Sep 15
0
[LLVMdev] problem with sgt's on Sparc machine
...t; wrote:
> Hi guys,
>
> Thanks for the input. However, it seems that the code still produces the
> wrong output on a Sparc machine.
>
> My current llvm_print.bc code is:
> --------------------------------------------------------------------------------------------------
> ; MduleID = '<stdin>'
> target datalayout =
> "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-n32"
> target triple = "sparc-unknown-linux"
>
> @P = global i32 1
> @dP = global i32 1
>
> @.str = private constant...
2011 Sep 16
2
[LLVMdev] problem with sgt's on Sparc machine
...>
>> Thanks for the input. However, it seems that the code still produces the
>> wrong output on a Sparc machine.
>>
>> My current llvm_print.bc code is:
>> --------------------------------------------------------------------------------------------------
>> ; MduleID = '<stdin>'
>> target datalayout =
>> "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-n32"
>> target triple = "sparc-unknown-linux"
>>
>> @P = global i32 1
>> @dP = global i32 1
>>
&g...
2011 Sep 15
0
[LLVMdev] problem with sgt's on Sparc machine
On Thu, Sep 15, 2011 at 11:06 AM, Christine Cheng <clcheng at stanford.edu> wrote:
> Hi Duncan,
>
> Thanks for the reply! There is no LLVM on the Sparc machine so I cannot
> compile my code there into .s file. How shall I modify the target data
> layout and triple so it works on Sparc? Basically I got these from compiling
> C code using llvm-gcc.
You can use clang for
2011 Sep 16
0
[LLVMdev] problem with sgt's on Sparc machine
...nput. However, it seems that the code still produces the
> >> wrong output on a Sparc machine.
> >>
> >> My current llvm_print.bc code is:
> >>
> --------------------------------------------------------------------------------------------------
> >> ; MduleID = '<stdin>'
> >> target datalayout =
> >>
> "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-n32"
> >> target triple = "sparc-unknown-linux"
> >>
> >> @P = global i32 1
> >...
2011 Sep 15
2
[LLVMdev] problem with sgt's on Sparc machine
Hi Duncan,
Thanks for the reply! There is no LLVM on the Sparc machine so I cannot
compile my code there into .s file. How shall I modify the target data
layout and triple so it works on Sparc? Basically I got these from compiling
C code using llvm-gcc.
Best,
Christine
On Thu, Sep 15, 2011 at 10:20 AM, Duncan Sands <baldrick at free.fr> wrote:
> Hi,
>
> > target datalayout =
2011 Sep 15
2
[LLVMdev] problem with sgt's on Sparc machine
Hi,
I compiled the following code on a Sparc machine, basically it produce
different results than a X86 machine.
-------------------------------------------------------------------------------------------------------------------
; MduleID = '<stdin>'
target datalayout =
"e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32-n8:16:32"
target triple = "i386-pc-linux-gnu"
@P = global i32 1
@dP = global i32 1
@.str = private constant [4 x...