Displaying 3 results from an estimated 3 matches for "_ashldi3".
Did you mean:
__ashldi3
2005 Mar 17
1
icecast on an Intel XScale ARM processor
...bedix/tools/arm-linux/lib/ld-linux.so.2(.text+0x11250): first defined here
/opt/Embedix/tools/arm-linux/lib/ld-linux.so.2(*IND*+0x0): multiple definition of `__fxstat64'
/opt/Embedix/tools/arm-linux/lib/ld-linux.so.2(.text+0x1142c): first defined here
/opt/Embedix/tools/arm-linux/bin/ld: Error: _ashldi3.o uses hard floating point, whereas icecast uses soft floating point
File format not recognized: failed to merge target specific data of file /opt/Embedix/tools/lib/gcc-lib/arm-linux/2.95.2/libgcc.a(_ashldi3.o)
/opt/Embedix/tools/arm-linux/bin/ld: Error: _lshrdi3.o uses hard floating point, whereas...
2009 Jun 04
1
[LLVMdev] endian issue of llvm-gcc and llvm backend
Hi, all
As I'm a Chinese, be patient of my poor description below.
I compiled libgcc into llvm bitcode in both big endian and little endian.
and got 2 different version of function: _ashldi3, the following is the
fragment of this function:
little endian:
=============================================
......
target datalayout =
"e-p:32:32:32-i1:8:8-i8:8:32-i16:16:32-i32:32:32-i64:32:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64"
target triple = "nds32le-linux"...
2009 Jun 05
0
[LLVMdev] endian issue of llvm-gcc and llvm backend
...9 3:14:28 AM
> Subject: [LLVMdev] endian issue of llvm-gcc and llvm backend
>
> Hi, all
>
> As I'm a Chinese, be patient of my poor description below.
>
> I compiled libgcc into llvm bitcode in both big endian and little endian.
> and got 2 different version of function: _ashldi3, the following is the
> fragment of this function:
>
> little endian:
> =============================================
> ......
> target datalayout =
> "e-p:32:32:32-i1:8:8-i8:8:32-i16:16:32-i32:32:32-i64:32:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64"
> t...