Repo Added
|
Files
89
|
Badge
Embed ▾
README BADGES
|
push
github
Fix TDUP load forwarding after table rehash. Reported by Sergey Kaplun. (cherry-picked from commit c7db8255e) After table rehashing number keys loaded via ALOAD may be placed in the hash part of the table. So, load forwarding analysis missed the corresponding stores like they never existed. In that case, either we faced an assertion failure in `fwd_ahload()` due to value types mismatch, or we faced an assertion failure in `rec_check_slots()` since the forwarded value by the JIT compiler isn't the same as it is in the interpreter. This patch adds a check that there is no `IR_NEWREF` after table creation, so it can't be rehashed. Sergey Kaplun: * added the description and the test for the problem Part of tarantool/tarantool#8825
5332 of 5969 branches covered (0.0%)
Branch coverage included in aggregate %.
4 of 4 new or added lines in 1 file covered. (100.0%)
20455 of 23287 relevant lines covered (87.84%)
1286298.27 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|
Builds | Branch | Commit | Type | Ran | Committer | Via | Coverage |
---|---|---|---|---|---|---|---|
6009642491 | skaplun/lj-980-load-fwd-after-table-rehash | Fix TDUP load forwarding after table rehash. Reported by Sergey Kaplun. (cherry-picked from commit c7db8255e) After table rehashing number keys loaded via ALOAD may be placed in the hash part of the table. So, loa... | push | igormunkin | github |
88.14 |