From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: tarantool-patches@freelists.org,
Alexander Turenko <alexander.turenko@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2 0/4] luajit: Bacport patches from openrusty
Date: Thu, 23 May 2019 14:53:28 +0300 [thread overview]
Message-ID: <20190523115328.GE11013@uranus> (raw)
In-Reply-To: <20190523105703.cqsz6bykgw6ya6jy@tarantool.org>
On Thu, May 23, 2019 at 01:57:03PM +0300, Kirill Yukhin wrote:
>
> > You know I've noticed that openrusy has another bug fix for that
> > named unsink 64bit pointers, I backported it too but didn't reveal
> > any difference when was running tests, so I desided to not include
> > it for a while.
>
> I guess that's connected to GC64, which is enabled on OSX only for
> Tarantool. IMHO, need to give it a try on OSX.
OK, I'll send it as a separate today evening.
prev parent reply other threads:[~2019-05-23 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 19:05 [tarantool-patches] " Cyrill Gorcunov
2019-05-22 19:05 ` [tarantool-patches] [PATCH luajit v2 1/4] Fix overflow of snapshot map offset Cyrill Gorcunov
2019-05-22 19:05 ` [tarantool-patches] [PATCH luajit v2 2/4] Fix rechaining of pseudo-resurrected string keys Cyrill Gorcunov
2019-05-22 19:05 ` [tarantool-patches] [PATCH luajit v2 3/4] bugfix: LuaJIT tables' hash chains might get corrupted leading to infinite loops while fetching, missing keys, and etc Cyrill Gorcunov
2019-05-22 19:05 ` [tarantool-patches] [PATCH tarantool v2 4/4] test/luajit-tap: Add table_chain_bug_LuaJIT_494.test.lua Cyrill Gorcunov
2019-05-23 10:32 ` [tarantool-patches] Re: [PATCH v2 0/4] luajit: Bacport patches from openrusty Kirill Yukhin
2019-05-23 10:37 ` Cyrill Gorcunov
2019-05-23 10:57 ` Kirill Yukhin
2019-05-23 11:53 ` Cyrill Gorcunov [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=20190523115328.GE11013@uranus \
--to=gorcunov@gmail.com \
--cc=alexander.turenko@tarantool.org \
--cc=kyukhin@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v2 0/4] luajit: Bacport patches from openrusty' \
/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