From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Bronnikov <sergeyb@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit 2/2] Avoid negation of signed integers in C that may hold INT*_MIN. Date: Thu, 4 Jul 2024 11:40:31 +0300 [thread overview] Message-ID: <ZoZf_4S29wmQmnRR@root> (raw) In-Reply-To: <e83e9d93-7e68-4d71-9b3d-5ce2f5a345cc@tarantool.org> Hi, Sergey! Thanks for the review! Fixed your comments rebased to the tarantool/master and force-pushed the branch. On 04.07.24, Sergey Bronnikov wrote: > Hi, Sergey, > > thanks for the patch! LGTM with nit below > > > On 25.06.2024 18:54, Sergey Kaplun wrote: > > From: Mike Pall <mike> <snipped> > > diff --git a/test/tarantool-tests/lj-928-int-min-negation.test.lua b/test/tarantool-tests/lj-928-int-min-negation.test.lua > > new file mode 100644 > > index 00000000..26f4ed8e > > --- /dev/null > > +++ b/test/tarantool-tests/lj-928-int-min-negation.test.lua > > @@ -0,0 +1,121 @@ > > +local tap = require('tap') > > + > > +-- Test file to demonstrate LuaJIT's UBSan failures during > > +-- `INT*_MIN` negation. > > +-- See also:https://github.com/LuaJIT/LuaJIT/issues/928. > > + > > +local test = tap.test('lj-928-int-min-negation.'):skipcond({ > > dot could be omitted in a test's name. Fixed, thanks! =================================================================== diff --git a/test/tarantool-tests/lj-928-int-min-negation.test.lua b/test/tarantool-tests/lj-928-int-min-negation.test.lua index 982bba73..bdf7e4f0 100644 --- a/test/tarantool-tests/lj-928-int-min-negation.test.lua +++ b/test/tarantool-tests/lj-928-int-min-negation.test.lua @@ -4,7 +4,7 @@ local tap = require('tap') -- `INT*_MIN` negation. -- See also: https://github.com/LuaJIT/LuaJIT/issues/928. -local test = tap.test('lj-928-int-min-negation.'):skipcond({ +local test = tap.test('lj-928-int-min-negation'):skipcond({ ['Test requires JIT enabled'] = not jit.status(), }) =================================================================== > > <snipped> -- Best regards, Sergey Kaplun
next prev parent reply other threads:[~2024-07-04 8:40 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-25 15:54 [Tarantool-patches] [PATCH luajit 0/2] Fix UBSan warnings Sergey Kaplun via Tarantool-patches 2024-06-25 15:54 ` [Tarantool-patches] [PATCH luajit 1/2] Prevent sanitizer warning in snap_restoredata() Sergey Kaplun via Tarantool-patches 2024-07-01 8:44 ` Maxim Kokryashkin via Tarantool-patches 2024-07-04 7:58 ` Sergey Bronnikov via Tarantool-patches 2024-07-04 8:41 ` Sergey Kaplun via Tarantool-patches 2024-07-04 14:59 ` Sergey Bronnikov via Tarantool-patches 2024-06-25 15:54 ` [Tarantool-patches] [PATCH luajit 2/2] Avoid negation of signed integers in C that may hold INT*_MIN Sergey Kaplun via Tarantool-patches 2024-07-01 9:11 ` Maxim Kokryashkin via Tarantool-patches 2024-07-01 10:12 ` Sergey Kaplun via Tarantool-patches 2024-07-04 8:08 ` Sergey Bronnikov via Tarantool-patches 2024-07-04 8:40 ` Sergey Kaplun via Tarantool-patches [this message] 2024-07-04 14:59 ` Sergey Bronnikov via Tarantool-patches 2024-07-09 8:08 ` [Tarantool-patches] [PATCH luajit 0/2] Fix UBSan warnings Sergey Kaplun via Tarantool-patches 2024-07-09 8:15 ` 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=ZoZf_4S29wmQmnRR@root \ --to=tarantool-patches@dev.tarantool.org \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 2/2] Avoid negation of signed integers in C that may hold INT*_MIN.' \ /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