Ran
|
Jobs
1
|
Files
89
|
Run time
11s
|
Badge
README BADGES
|
push
github
Fix HREFK forwarding vs. table.clear(). Reported by XmiliaH. (cherry-picked from commit d5a237eae) When performing HREFK (and also ALOAD, HLOAD) forwarding optimization, the `table.clear()` function call may be performed on the table operand from HREFK between table creation and IR, from which value is forwarded. This call isn't taken in the account, so it may lead to too optimistic value-forwarding from NEWREF (and also ASTORE, HSTORE), or the omitted type guard for HREFK operation. Therefore, this leads to incorrect trace behaviour (for example, taking a non-nil value from the cleared table). This patch adds necessary checks for `table.clear()` calls. Sergey Kaplun: * added the description and the test for the problem Part of tarantool/tarantool#9145 Reviewed-by: Maxim Kokryashkin <m.kokryashkin@tarantool.org> Reviewed-by: Sergey Bronnikov <sergeyb@tarantool.org> Signed-off-by: Igor Munkin <imun@tarantool.org> (cherry picked from commit aed147cd9)
5348 of 5968 branches covered (0.0%)
Branch coverage included in aggregate %.
12 of 12 new or added lines in 1 file covered. (100.0%)
21 existing lines in 4 files now uncovered.20515 of 23266 relevant lines covered (88.18%)
697727.15 hits per line
Lines | Coverage | ∆ | File |
---|---|---|---|
1 |
93.42 |
0.0% | src/lj_ir.c |
1 |
92.11 |
0.0% | src/lj_vmmath.c |
2 |
72.64 |
-0.17% | src/lj_crecord.c |
17 |
89.11 |
-1.77% | src/lj_ffrecord.c |
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 7119175140.1 | 89 |
88.47 |
GitHub Action Run |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|