Displaying 2 results from an estimated 2 matches for "ea9c776".
Did you mean:
ea9c776e
2014 Jul 05
2
[LLVMdev] LLVM commit 410f38e01597120b41e406ec1cea69127463f9e5
Hi,
I'm working on a target which have a variable size for CC (the same size as
the arguments). As a result getSetCCResultType, return a variable size.
In this commit, at the line DAG.getSExtOrTrunc(SetCC, DL, SelectVT), on my
target, you end up generating the Node you are replacing, and so creating a
loop in the DAG, which give a whole new meaning to the A in the acronym.
Subsequent code
2014 Jul 06
2
[LLVMdev] LLVM commit 410f38e01597120b41e406ec1cea69127463f9e5
...ResultType is i64 for i64, and i32 for i32, so using the type
> of the sext created i64 (setcc (i32 x) (i32 y)) which doesn't work
>
> -Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140705/ea9c776e/attachment.html>