the code in expr_cond save nocode_wanted around some parts of expression evaluation, but at the wrong spots. If the evaluation of the condition itself (e.g. in the testcase the first whole ternary expression) resulted in CODE_OFF, then that was saved, and restored before return, even if in-between codegen would have CODE_ON'ed already. Thus the whole CODE_OFF state bled out to outside the expression evaluation and also disabled the whole if-block. Found by yarpgen v1 (seed 64).
Showing the changes to tests (2 of 3 files). Show all
Unified · Split
| @@ -39,6 +39,17 @@ static int getme(struct condstruct* s, int i) · 38 unmodified lines | ||
| 39 | 39 | return i1 + i2 + i3 + i4; |
| 40 | 40 | } |
| 41 | 41 | |
| 42 | +int someglobal; | |
| 43 | + | |
| 44 | +void constantcond(void) | |
| 45 | +{ | |
| 46 | + /* This was broken by 8227db3a2, it saved/restored the CODE_OFF state | |
| 47 | + during the expression and that bled out to the outer one disabling | |
| 48 | + codegen for if-body. */ | |
| 49 | + if (( (someglobal ? 0 : 0) ? 8 : 9)) | |
| 50 | + printf("okay\n"); | |
| 51 | +} | |
| 52 | + | |
| 42 | 53 | int main() |
| 43 | 54 | { |
| 44 | 55 | int Count; |
| @@ -73,6 +84,8 @@ int main() · 28 unmodified lines | ||
| 73 | 84 | //0 ? a : 0.0; |
| 74 | 85 | } |
| 75 | 86 | |
| 87 | + constantcond(); | |
| 88 | + | |
| 76 | 89 | |
| 77 | 90 | return 0; |
| 78 | 91 | } |
| @@ -10,3 +10,4 @@ · 9 unmodified lines | ||
| 10 | 10 | 24 |
| 11 | 11 | 27 |
| 12 | 12 | 152 |
| 13 | +okay | |