search for: operationaction

...now seeing failures in our back end because clang is emitting them, they're travelling through the IR to the SelectionDAG, and there's nothing to match them. Trying to match them, I get an error from TableGen saying: Variable not defined: 'addrspacecast' If I try to set a custom OperationAction in the target lowering class for ISD::ADDRSPACECAST, I never see LowerOperation invoked with that opcode (or with any other unknown operations). So what is the correct way of matching these nodes? David

...b call from the Custom lowering implementation; I am not going to strongly suggest how to solve this problem, but just to state that there’s an actual problem or at least an oddity on the way that shifts are (or can be) dealt with. To me, the first thing we need to do is to actually have LibCall operationActions working for shifts. This is also as a matter of code consistency if you want, and doing this alone doesn’t break anything: ultimately it’s the responsibility of the target to chose whether it uses it or not. Additionally, we should specify a way to fall through to LibCall lowering from a Custom l...

...approaching this from the wrong way, but I don't think this transformation should be that difficult. Basically I want dst = select $LHS, $RHS, $TVAL, $FVAL, $condOp to be transformed into $condOp tmp, $LHS, $RHS cmov_logical dst, tmp, $TVAL, $FVAL My attempt at doing so with a custom OperationAction also failed. So, what would I need to do to figure out how to implement this correctly? Is there any place you can point me to which shows how to go from a single instruction to multiple consecutive instructions? A function that I can study would be nice since my problem is even though I can look a...

...r Shifts, but they can’t be used because there’s an omission in the sources. I only proposed to add a missing case statement to the ConvertNodeToLibCall. To my understanding this is totally harmless to any existing or future targets because all what it does is to call the Library function when setOperationAction is set to “LibCall”. This is not different that any other case, and you just confirmed that you added the same for the CTLZ… functions. So I do not understand what you mean by “terrible quality in a lot of cases”: Targets with native shift support are not affected, and neither are targets with cu...