From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Kaplun <skaplun@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit] Fix TDUP load forwarding after table rehash. Date: Thu, 31 Aug 2023 15:19:30 +0000 [thread overview] Message-ID: <ZPCvgrqQjKA1ZD+G@tarantool.org> (raw) In-Reply-To: <20230817144641.20088-1-skaplun@tarantool.org> Sergey, I've checked the patchset into all long-term branches in tarantool/luajit and bumped a new version in master, release/2.11 and release/2.10. On 17.08.23, Sergey Kaplun via Tarantool-patches wrote: > From: Mike Pall <mike> > > Reported by Sergey Kaplun. > > (cherry-picked from commit c7db8255e1eb59f933fac7bc9322f0e4f8ddc6e6) > > 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 are never existed. In such case, either > we faced an assertion failure in `fwd_ahload()` due to values types > mismatch, either we faced an assertion failure in `rec_check_slots()` > since 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 any `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 > --- > > Branch: https://github.com/tarantool/luajit/tree/skaplun/lj-980-load-fwd-after-table-rehash > PR: https://github.com/tarantool/tarantool/pull/8998 > Related issues: > * https://github.com/LuaJIT/LuaJIT/issues/980 > * https://github.com/tarantool/tarantool/issues/8825 > > src/lj_opt_mem.c | 6 + > ...j-980-load-fwd-after-table-rehash.test.lua | 166 ++++++++++++++++++ > 2 files changed, 172 insertions(+) > create mode 100644 test/tarantool-tests/lj-980-load-fwd-after-table-rehash.test.lua > <snipped> > -- > 2.41.0 > -- Best regards, IM
prev parent reply other threads:[~2023-08-31 15:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-17 14:46 Sergey Kaplun via Tarantool-patches 2023-08-20 12:13 ` Maxim Kokryashkin via Tarantool-patches 2023-08-21 8:58 ` Sergey Kaplun via Tarantool-patches 2023-08-28 14:25 ` Sergey Bronnikov via Tarantool-patches 2023-08-28 14:26 ` Sergey Kaplun via Tarantool-patches 2023-08-28 14:33 ` Sergey Bronnikov via Tarantool-patches 2023-08-31 15:19 ` Igor Munkin via Tarantool-patches [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=ZPCvgrqQjKA1ZD+G@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=imun@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit] Fix TDUP load forwarding after table rehash.' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox