| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-08-22 | Match scalar-pair-bool more flexibly for LLVM 11 | Josh Stone | -2/+3 | |
| LLVM 11 started using `phi` and `select` for `fn pair_i32_bool`, which is still valid, but harder to match than the simple instructions we were getting before. We'll just check that the unpacked args are directly referenced in any way, and call it good. | ||||
| 2019-09-13 | codegen: use "_N" (like for other locals) instead of "argN", for argument names. | Eduard-Mihai Burtescu | -6/+6 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -10/+0 | |
| 2018-07-05 | Update scalar pairs per review comments | Josh Stone | -0/+14 | |
| 2018-07-05 | Store scalar pair bools as i8 in memory | Josh Stone | -0/+40 | |
| We represent `bool` as `i1` in a `ScalarPair`, unlike other aggregates, to optimize IR for checked operators and the like. With this patch, we still do so when the pair is an immediate value, but we use the `i8` memory type when the value is loaded or stored as an LLVM aggregate. So `(bool, bool)` looks like an `{ i1, i1 }` immediate, but `{ i8, i8 }` in memory. When a pair is a direct function argument, `PassMode::Pair`, it is still passed using the immediate `i1` type, but as a return value it will use the `i8` memory type. Also, `bool`-like` enum tags will now use scalar pairs when possible, where they were previously excluded due to optimization issues. | ||||
