Ran
|
Jobs
1
|
Files
89
|
Run time
1min
|
Badge
Embed ▾
README BADGES
|
push
github
Check frame size limit before returning to a lower frame. Thanks to Sergey Kaplun. (cherry picked from commit 302366a33) When compiling a stitched (or side) trace, there is no check for the frame size of the current prototype during recording. Hence, when we return (for example, after stitching) to the lower frame with a maximum possible frame size (249), the 251 = `baseslot` (2) + `maxslot` (249) slot for GC64 mode may be used. This leads to the corresponding assertion failure in `rec_check_slots()`. This patch adds the corresponding check. The `LJ_MAX_JSLOTS` and `LJ_MAX_SLOTS` are equal by default, but their values may be manually changed for some custom builds. Hence, the check is not enabled only for `LJ_GC64` mode. Sergey Kaplun: * added the description and the test for the problem Part of tarantool/tarantool#9595
5658 of 6017 branches covered (94.03%)
Branch coverage included in aggregate %.
2 of 2 new or added lines in 1 file covered. (100.0%)
9 existing lines in 3 files now uncovered.21602 of 23411 relevant lines covered (92.27%)
2816571.7 hits per line
Lines | Coverage | ∆ | File |
---|---|---|---|
1 |
77.24 |
-0.08% | src/lj_opt_fold.c |
2 |
93.09 |
-0.99% | src/lj_ir.c |
6 |
94.74 |
-4.31% | src/lj_str.c |
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 8264767798.1 | 89 |
92.63 |
GitHub Action Run |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|