Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Igor Munkin <imun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 2/3] ci: introduce workflow for exotic builds
Date: Wed, 1 Feb 2023 11:52:56 +0300	[thread overview]
Message-ID: <Y9ooaNzo4qggvvKy@root> (raw)
In-Reply-To: <Y9oicT14tn/MaPmO@tarantool.org>

Hi, Igor!

Thanks for reply:)!

On 01.02.23, Igor Munkin wrote:
> Hi everyone,
> 
> On 30.01.23, Sergey Kaplun wrote:
> 
> <snipped>
> 
> > > 
> > > Shall we add the -DLUAJIT_ENABLE_CHECKHOOK and -DLUAJIT_SMART_STRINGS=1 since they are in Tarantool by default?
> > 
> > -DLUAJIT_SMART_STRINGS=1 is set by default, so it's OK not to set it
> > mannually.
> > 
> > OTOH, -DLUAJIT_ENABLE_CHECKHOOK is not set by default.
> > I prefer not to set it for this particular workflow, because I plan to
> > use it for very specific builds (even impossible for Tarantool) for
> > example with -DLUAJIT_DISABLE_JIT=ON, -DLUAJIT_DISABLE_FFI=ON flags.
> > Also, this flag is not set for default LuaJIT testing, so I tried to
> > make those workflows look similar.
> > But if we want to add this flag for default build or testing we should
> > add it for this workflow too.
> > CC-ed Igor to hear his opinion.
> 
> I'm totally for adding such workflows, but I suggest to do it in a
> separate patch. Sergey, this is on you.

OK, so I'll add exotic -DLUAJIT_ENBALE_CHECKHOOK job after this patch
will be merged to avoid rebases.

> 
> > 
> > > 
> 
> <snipped>
> 
> > 
> > -- 
> > Best regards,
> > Sergey Kaplun
> 
> -- 
> Best regards,
> IM

-- 
Best regards,
Sergey Kaplun

  reply	other threads:[~2023-02-01  8:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 20:19 [Tarantool-patches] [PATCH luajit 0/3] Dualnumber mode fixes Sergey Kaplun via Tarantool-patches
2023-01-18 20:16 ` [Tarantool-patches] [PATCH luajit 1/3] sysprof: fix interval parsing in dual-number mode Sergey Kaplun via Tarantool-patches
2023-01-24 14:16   ` Maxim Kokryashkin via Tarantool-patches
2023-01-26 15:55   ` sergos via Tarantool-patches
2023-01-30  9:39     ` Sergey Kaplun via Tarantool-patches
2023-01-18 20:16 ` [Tarantool-patches] [PATCH luajit 2/3] ci: introduce workflow for exotic builds Sergey Kaplun via Tarantool-patches
2023-01-24 14:20   ` Maxim Kokryashkin via Tarantool-patches
2023-01-26 21:12   ` sergos via Tarantool-patches
2023-01-30  9:51     ` Sergey Kaplun via Tarantool-patches
2023-02-01  8:27       ` Igor Munkin via Tarantool-patches
2023-02-01  8:52         ` Sergey Kaplun via Tarantool-patches [this message]
2023-02-02  8:54           ` sergos via Tarantool-patches
2023-01-18 20:16 ` [Tarantool-patches] [PATCH luajit 3/3] x86/x64: Fix loop realignment Sergey Kaplun via Tarantool-patches
2023-01-19 10:17   ` Sergey Kaplun via Tarantool-patches
2023-01-24 15:13   ` Maxim Kokryashkin via Tarantool-patches
2023-01-26  7:06     ` Sergey Kaplun via Tarantool-patches
2023-01-26 14:45       ` Maxim Kokryashkin via Tarantool-patches
2023-01-26 21:22       ` sergos via Tarantool-patches
2023-02-20  9:56 ` [Tarantool-patches] [PATCH luajit 0/3] Dualnumber mode fixes 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=Y9ooaNzo4qggvvKy@root \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=imun@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit 2/3] ci: introduce workflow for exotic builds' \
    /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