From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Bronnikov <sergeyb@tarantool.org>
Cc: Maksim Tiushev <mandesero@gmail.com>,
tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v5 luajit 1/3] Ensure full init of IR_NOP instructions.
Date: Mon, 16 Dec 2024 14:24:02 +0300 [thread overview]
Message-ID: <Z2AN0gWpU3px0LOd@root> (raw)
In-Reply-To: <dc58fcd7-104c-4925-81d6-a94a26f8cf73@tarantool.org>
Hi, Sergey!
Thanks for the review!
On 13.12.24, Sergey Bronnikov wrote:
> Hello, Sergey,
>
> thanks for the patch! LGTM with a minor comment.
>
> On 11.12.2024 16:21, Sergey Kaplun wrote:
> > From: Mike Pall <mike>
> >
> > (cherry picked from commit de6b1a11dd1a3349179084578c5d533be1c30234)
> >
> > Before this patch, Valgrind produces tons of warnings during the VMevent
> > calls since the `IR_NOP` instruction isn't fully initialized. Hence, any
> > parsing operations for it in handlers during `jit.dump()` leads to the
> > "uninitialised value" error. This patch fixes the issue by the proper
> > init of such IRs.
>
> Please add to a comment that with these tests the problem could
>
> be reproduced:
>
> test/tarantool-tests/lj-1128-table-new-opt-tnew.test.lua
>
> test/tarantool-tests/fix-jit-dump-ir-conv.test.lua
>
> test/tarantool-tests/unit-jit-parse.test.lua
Updated. The new commit message is the following:
| Ensure full init of IR_NOP instructions.
|
| (cherry picked from commit de6b1a11dd1a3349179084578c5d533be1c30234)
|
| Before this patch, Valgrind produces tons of warnings during the VMevent
| calls since the `IR_NOP` instruction isn't fully initialized. Hence, any
| parsing operations for it in handlers during `jit.dump()` leads to the
| "uninitialised value" error.
|
| This can be reproduced with the following tests from the
| tarantool-tests suite:
| * fix-jit-dump-ir-conv.test.lua
| * lj-1128-table-new-opt-tnew.test.lua
| * lj-981-folding-0.test.lua
| * unit-jit-parse.test.lua
|
| This patch fixes the issue by the proper init of such IRs.
|
| Sergey Kaplun:
| * added the description for the problem
|
| Needed for tarantool/tarantool#3705
| Part of tarantool/tarantool#10709
>
> >
> > Sergey Kaplun:
> > * added the description for the problem
> >
> > Needed for tarantool/tarantool#3705
> > Part of tarantool/tarantool#10709
> > ---
<snipped>
--
Best regards,
Sergey Kaplun
next prev parent reply other threads:[~2024-12-16 11:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 13:21 [Tarantool-patches] [PATCH v5 luajit 0/3] Valgrind testing Sergey Kaplun via Tarantool-patches
2024-12-11 13:21 ` [Tarantool-patches] [PATCH v5 luajit 1/3] Ensure full init of IR_NOP instructions Sergey Kaplun via Tarantool-patches
2024-12-13 12:54 ` Sergey Bronnikov via Tarantool-patches
2024-12-16 11:24 ` Sergey Kaplun via Tarantool-patches [this message]
2024-12-17 11:08 ` Sergey Bronnikov via Tarantool-patches
2025-01-09 7:04 ` mandesero--- via Tarantool-patches
2024-12-11 13:21 ` [Tarantool-patches] [PATCH v5 luajit 2/3] cmake: run tests with Valgrind Sergey Kaplun via Tarantool-patches
2024-12-13 13:18 ` Sergey Bronnikov via Tarantool-patches
2024-12-16 16:40 ` Sergey Kaplun via Tarantool-patches
2024-12-17 11:42 ` Sergey Bronnikov via Tarantool-patches
2024-12-17 12:17 ` Sergey Kaplun via Tarantool-patches
2024-12-17 19:31 ` Sergey Bronnikov via Tarantool-patches
2025-01-09 7:03 ` mandesero--- via Tarantool-patches
2024-12-11 13:21 ` [Tarantool-patches] [PATCH v5 luajit 3/3] ci: add Valgrind testing workflow Sergey Kaplun via Tarantool-patches
2024-12-13 13:23 ` Sergey Bronnikov via Tarantool-patches
2024-12-22 7:44 ` mandesero--- via Tarantool-patches
2025-01-31 9:27 ` [Tarantool-patches] [PATCH v5 luajit 0/3] Valgrind testing Sergey Kaplun via Tarantool-patches
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=Z2AN0gWpU3px0LOd@root \
--to=tarantool-patches@dev.tarantool.org \
--cc=mandesero@gmail.com \
--cc=sergeyb@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v5 luajit 1/3] Ensure full init of IR_NOP instructions.' \
/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