From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: "Максим Корякшин" <m.kokryashkin@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit v2] luajit-gdb: support dualnum mode Date: Tue, 17 Aug 2021 10:47:41 +0300 [thread overview] Message-ID: <20210817074741.GB5743@tarantool.org> (raw) In-Reply-To: <1629108103.120226674@f190.i.mail.ru> Max, Thanks for the fixes! LGTM now. BTW, I've reverted one fix proposed by Sergey (see the corresponding thread) and fixed a typo below. On 16.08.21, Максим Корякшин wrote: > > Hello, Igor! > Thanks for your comments! > > Here is the new commit message: > ========================================================= > gdb: support LJ_DUALNUM mode > > luajit-gdb.py displays integers in LJ_DUALNUM mode as nan-s. The > dumper function produces output considering any input value as a > double. However, in LJ_DUALNUM mode, integers and doubles are stored > differently, so the `itype` of a double must be less than > `LJ_TISNUM`, and the `itype` of an integer must be `LJ_TISNUM`. With > this fact in mind, we can easily differentiate one from another. > > Closes tarantool/tarantool#6224 > ========================================================= > > Here is the diff: > ========================================================= > diff --git a/src/luajit-gdb.py b/src/luajit-gdb.py > index 9ccca66a..25428745 100644 > --- a/src/luajit-gdb.py > +++ b/src/luajit-gdb.py > @@ -507,10 +507,14 @@ pointers respectively. > ''' > def invoke(self, arg, from_tty): > - gdb.write('LJ_64: {LJ_64}, LJ_GC64: {LJ_GC64}\n'.format( > - LJ_64 = LJ_64, > - LJ_GC64 = LJ_GC64 > - )) > + gdb.write( > + 'LJ_64: {LJ_64}, LJ_GC64: {LJ_GC64}, LJ_DUALNUM : {LJ_DUALNUM}\n' Side note: Excess whitespace. I've fixed this before merging the patch into the trunk. > + .format( > + LJ_64 = LJ_64, > + LJ_GC64 = LJ_GC64, > + LJ_DUALNUM = LJ_DUALNUM > + ) > + ) > class LJDumpTValue(LJBase): > ''' <snipped> > ========================================================= > > > <snipped> > >Best regards, > >Maxim Kokryashkin > > -- Best regards, IM
next prev parent reply other threads:[~2021-08-17 8:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-31 13:36 [Tarantool-patches] [PATCH luajit] " Maxim Kokryashkin via Tarantool-patches 2021-08-11 8:27 ` Sergey Kaplun via Tarantool-patches 2021-08-13 14:29 ` Максим Корякшин via Tarantool-patches 2021-08-14 11:38 ` [Tarantool-patches] [PATCH luajit v2] " Maxim Kokryashkin via Tarantool-patches 2021-08-14 13:36 ` Максим Корякшин via Tarantool-patches 2021-08-14 13:47 ` Sergey Kaplun via Tarantool-patches 2021-08-14 17:26 ` Максим Корякшин via Tarantool-patches 2021-08-17 7:56 ` Igor Munkin via Tarantool-patches 2021-08-16 8:49 ` Igor Munkin via Tarantool-patches 2021-08-16 10:01 ` Максим Корякшин via Tarantool-patches 2021-08-16 16:23 ` Vitaliia Ioffe via Tarantool-patches 2021-08-17 7:47 ` Igor Munkin via Tarantool-patches [this message] 2021-08-17 9:23 ` [Tarantool-patches] [PATCH luajit] " Igor Munkin 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=20210817074741.GB5743@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=imun@tarantool.org \ --cc=m.kokryashkin@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit v2] luajit-gdb: support dualnum mode' \ /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