Displaying 3 results from an estimated 3 matches for "idxprom9".
Did you mean:
idxprom
2013 Oct 28
2
[LLVMdev] loop vectorizer says Bad stride
...d i32* %i, align 4
%add5 = add nsw i32 256, %11
%idxprom6 = sext i32 %add5 to i64
%12 = load float** %a.addr, align 8
%arrayidx7 = getelementptr inbounds float* %12, i64 %idxprom6
%13 = load float* %arrayidx7, align 4
%14 = load i32* %i, align 4
%add8 = add nsw i32 256, %14
%idxprom9 = sext i32 %add8 to i64
%15 = load float** %b.addr, align 8
%arrayidx10 = getelementptr inbounds float* %15, i64 %idxprom9
%16 = load float* %arrayidx10, align 4
%add11 = fadd float %13, %16
%17 = load i32* %i, align 4
%add12 = add nsw i32 256, %17
%idxprom13 = sext i32 %add12...
2013 Oct 28
0
[LLVMdev] loop vectorizer says Bad stride
...%add5 = add nsw i32 256, %11
> %idxprom6 = sext i32 %add5 to i64
> %12 = load float** %a.addr, align 8
> %arrayidx7 = getelementptr inbounds float* %12, i64 %idxprom6
> %13 = load float* %arrayidx7, align 4
> %14 = load i32* %i, align 4
> %add8 = add nsw i32 256, %14
> %idxprom9 = sext i32 %add8 to i64
> %15 = load float** %b.addr, align 8
> %arrayidx10 = getelementptr inbounds float* %15, i64 %idxprom9
> %16 = load float* %arrayidx10, align 4
> %add11 = fadd float %13, %16
> %17 = load i32* %i, align 4
> %add12 = add nsw i32 256, %17
> %idxprom...
2017 May 21
4
Handling native i16 types in clang and opt
Hello.
My target architecture supports natively 16 bit integers (i16).
Whenever I write in C programs using only short types, clang compiles the program to
LLVM and converts the i16 data to i32 to perform arithmetic operations and then truncates
the results to i16. Then, the InstructionCombining (INSTCOMBINE or IC) pass removes these
conversions back and forth from i16, except for