Displaying 3 results from an estimated 3 matches for "foldandoffcmp".
Did you mean:
foldandoffcmps
2013 Apr 11
2
[LLVMdev] Bug in InstCombiner::FoldAndOfFCmps
...llvm/IR/Instructions.h, line 1117.
We begin with a float "a" and double "b":
> (fcmp oeq a, a) & (fcmp oeq b, b)
After canonicalization in InstCombine, we end up with the expression:
> (fcmp ord a, 0.0) & (fcmp ord b, 0.0)
The bug manifest is in InstCombiner::FoldAndOfFCmps(FCmpInst *LHS, FCmpInst
*RHS), when trying to perform this transformation:
> (fcmp ord x, c) & (fcmp ord y, c) -> (fcmp ord x, y)
This is all fine, except that the FCmpInst constructor in the IRBuilder
requires that both operands to the new fcmp are the same type, which they
are not....
2013 May 02
0
[LLVMdev] Bug in InstCombiner::FoldAndOfFCmps
On 11 April 2013 16:26, Cameron McInally <cameron.mcinally at nyu.edu> wrote:
> Hey guys,
>
> I've come across a bug when combining an AND of FCMPs. This bug occurs in my
> compiler as well as Clang built from trunk.
>
> A reduced test case is:
>
> int foo( float a, double b ) {
> return (a == a) & (b == b);
> }
>
> and the error is:
>
>
2013 May 02
1
[LLVMdev] Bug in InstCombiner::FoldAndOfFCmps
On 5/2/2013 4:20 PM, Rafael Espíndola wrote:
>
> I don't get any errors compiling this. Do you know if it was fixed? Do
> you get an error only for some particular target? What is the 'clang
> -cc1' command line that you seed in the error?
I see this error in our compiler, but not with the trunk. I guess it's
been fixed, but I don't know which commit did it.