Displaying 3 results from an estimated 3 matches for "lhsv".
Did you mean:
lhs
2009 Aug 11
2
[LLVMdev] Bug in optimization pass related to strcmp and big endian back-ends
..., 100 ; <i1> [#uses=1]
%1 = zext i1 %0 to i32 ; <i32> [#uses=1]
%2 = getelementptr [2 x i8]* @.str, i32 0, i32 %1
; <i8*> [#uses=1]
%tmp = bitcast i8* %2 to i16* ; <i16*>
[#uses=1]
%lhsv = load i16* %tmp, align 1 ; <i16>
[#uses=1]
%3 = icmp eq i16 %lhsv, 73 ; <i1> [#uses=1]
%4 = zext i1 %3 to i32 ; <i32> [#uses=1]
%5 = tail call i32 (i8*, ...)* @printf(i8* getelementptr ([4
x i8]* @.s...
2009 Aug 11
0
[LLVMdev] Bug in optimization pass related to strcmp and big endian back-ends
On Tue, Aug 11, 2009 at 1:13 AM, Stripf,
Timo<Timo.Stripf at itiv.uni-karlsruhe.de> wrote:
> On little endian machines the code works correct but on big endian %lhsv
> must be compared against 73 << 8.
If llvm-gcc thinks it's compiling for a little-endian target, the
optimizers will assume the target is little-endian... what are you
trying to do?
-Eli
2009 Aug 11
5
[LLVMdev] Bug in optimization pass related to strcmp and bigendian back-ends
...10:27
An: LLVM Developers Mailing List
Betreff: Re: [LLVMdev] Bug in optimization pass related to strcmp and bigendian back-ends
On Tue, Aug 11, 2009 at 1:13 AM, Stripf,
Timo<Timo.Stripf at itiv.uni-karlsruhe.de> wrote:
> On little endian machines the code works correct but on big endian %lhsv
> must be compared against 73 << 8.
If llvm-gcc thinks it's compiling for a little-endian target, the
optimizers will assume the target is little-endian... what are you
trying to do?
-Eli
_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc....