[CIR][CodeGen][Lower] CIR Unary Not Operation.

[redbopo]

Add Unary Not operation on CIRGen and Lowerings.

---

Most follow the work like #20
Currently not add LNot operation, since it requires the type to be cir.bool.

[bcardosolopes]

This looks pretty good, thanks.

[bcardosolopes]

Any specific reason on why not following LLVM's codegen? We usually try to match the skeleton as much as possible. Any reason why this wouldn't work?

Value *ScalarExprEmitter::VisitUnaryNot(const UnaryOperator *E) {
  TestAndClearIgnoreResultAssign();
  auto op = Visit(E->getSubExpr());
  // return buildUnaryOp ....
}

[bcardosolopes]

Thanks for the update.

I'm getting a bit confused with the way you are working with commits, for instance I don't understand what the purpose of the second commit here. You can re-organize your commits (squash, etc) and force push after you address a review. To speed up reviews: please make sure that any PR you send only contains one commit, add that they should be self-contained with change + test, you can always break things into multiple PRs.

[redbopo]

Thanks @bcardosolopes .
Usually I like to make multi commits on github if the following commits are concerned of the PR, or just small fix.
And next to use the native git squash merge provided by github.com to write these with a single commit.

I will fix with one commit one PR in clangir next.