From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Maxim Kokryashkin <m.kokryashkin@tarantool.org> Cc: Sergey Bronnikov <estetus@gmail.com>, tarantool-patches@dev.tarantool.org, max.kokryashkin@gmail.com Subject: Re: [Tarantool-patches] [PATCH 1/2] Fix embedded bytecode loader. Date: Sun, 6 Aug 2023 14:09:27 +0300 [thread overview] Message-ID: <ZM9_Z7xTB5soLX-Z@root> (raw) In-Reply-To: <5t3vejxwlcpd3fczyenum4527mtwtmt6qd4agwrxhnkt3zdtob@62fmw5pdbhqg> Hi, Max, Sergey! The patch is LGTM, after adding the test case (without additional CI job, if you don't want), see rational below. On 31.07.23, Maxim Kokryashkin wrote: > Hi, Sergey! <snipped> > > tests patch partially. > Typo: s/tests the patch/ > > Well, I've tried to run that test on x32 machine, and nothing happened. > I think we should backport this patch without tests then, since this > test seems irrelevant to the problem. What do you think? > > Also, it is kinda strange, that you are talking about a test in a patch > without any tests. You need to either mention that the test is present in > the next commit, or move that test here. The problem is perfectly repoduced for me if use instructions from [1]. I suppose that we should add this test, because it: 1) Shows the problem for the actual build that can be done by the user. 2) Still tests LuaJIT loader. > > > > Sergey Bronnikov: > > * added the description > > --- > > src/lj_bcread.c | 10 +++++----- > > src/lj_lex.c | 6 ++++++ > > src/lj_lex.h | 1 + > > 3 files changed, 12 insertions(+), 5 deletions(-) <snipped> > > -- > > 2.34.1 [1]: https://github.com/LuaJIT/LuaJIT/issues/549 -- Best regards, Sergey Kaplun
next prev parent reply other threads:[~2023-08-06 11:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-25 16:34 [Tarantool-patches] [PATCH 0/2] " Sergey Bronnikov via Tarantool-patches 2023-07-25 16:36 ` [Tarantool-patches] [PATCH 1/2] " Sergey Bronnikov via Tarantool-patches 2023-07-31 12:01 ` Maxim Kokryashkin via Tarantool-patches 2023-08-01 9:56 ` Sergey Bronnikov via Tarantool-patches 2023-08-06 11:09 ` Sergey Kaplun via Tarantool-patches [this message] 2023-08-15 8:51 ` Maxim Kokryashkin via Tarantool-patches 2023-07-25 16:37 ` [Tarantool-patches] [PATCH 2/2] Followup fix for " Sergey Bronnikov via Tarantool-patches 2023-07-31 12:20 ` Maxim Kokryashkin via Tarantool-patches 2023-08-01 9:53 ` Sergey Bronnikov via Tarantool-patches 2023-08-14 8:14 ` Sergey Bronnikov 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=ZM9_Z7xTB5soLX-Z@root \ --to=tarantool-patches@dev.tarantool.org \ --cc=estetus@gmail.com \ --cc=m.kokryashkin@tarantool.org \ --cc=max.kokryashkin@gmail.com \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 1/2] Fix embedded bytecode loader.' \ /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