diff options
| author | Luc Van Oostenryck <luc.vanoostenryck@gmail.com> | 2018-02-18 18:03:34 +0100 |
|---|---|---|
| committer | Luc Van Oostenryck <luc.vanoostenryck@gmail.com> | 2018-02-20 12:35:10 +0100 |
| commit | b8f9557e0834c8dfe26d64c0bbab3e226b4e75b1 (patch) | |
| tree | e8716d2416f4fe76329a55960f3645dbc47c66a7 /linearize.c | |
| parent | 90bf63e9779623488d02febf2dc8293b55283691 (diff) | |
| download | sparse-dev-b8f9557e0834c8dfe26d64c0bbab3e226b4e75b1.tar.gz | |
ban use of 'true' or 'false'
The idea being, of course, to be able for some functions to return
a bool, making clear what's their possible returned values.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Diffstat (limited to 'linearize.c')
| -rw-r--r-- | linearize.c | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/linearize.c b/linearize.c index eb4e68c2..211dabf4 100644 --- a/linearize.c +++ b/linearize.c @@ -1367,19 +1367,19 @@ static pseudo_t linearize_cond_branch(struct entrypoint *ep, struct expression * static pseudo_t linearize_select(struct entrypoint *ep, struct expression *expr) { - pseudo_t cond, true, false, res; + pseudo_t cond, valt, valf, res; struct instruction *insn; - true = linearize_expression(ep, expr->cond_true); - false = linearize_expression(ep, expr->cond_false); + valt = linearize_expression(ep, expr->cond_true); + valf = linearize_expression(ep, expr->cond_false); cond = linearize_expression(ep, expr->conditional); insn = alloc_typed_instruction(OP_SEL, expr->ctype); if (!expr->cond_true) - true = cond; + valt = cond; use_pseudo(insn, cond, &insn->src1); - use_pseudo(insn, true, &insn->src2); - use_pseudo(insn, false, &insn->src3); + use_pseudo(insn, valt, &insn->src2); + use_pseudo(insn, valf, &insn->src3); res = alloc_pseudo(insn); insn->target = res; |