List for cgit developers and users
 help / color / mirror / Atom feed
From: chighland at gmail.com (Coda Highland)
Subject: cgit-lua: to jit or not to jit
Date: Tue, 14 Jan 2014 12:50:35 -0800	[thread overview]
Message-ID: <CAFE_sBGWtjk-qRAHQGLNyjYJEfiswno1zWqkWFz50axCgsSN=A@mail.gmail.com> (raw)
In-Reply-To: <CAFE_sBHknnH_VAMebGzvk05T6b00T1BhbXs73gJPNNwUKBjVXg@mail.gmail.com>

On Tue, Jan 14, 2014 at 12:50 PM, Coda Highland <chighland at gmail.com> wrote:
> On Tue, Jan 14, 2014 at 12:41 PM, Eric Wing <ewmailing at gmail.com> wrote:
>>> But perhaps there
>>> are some obvious downsides to this approach that I also am missing.
>>
>> Here are a few more potential downsides not mentioned so far.
>>
>> One is that iOS and Windows Store policies disallow JIT. While you can
>> disable this part in LuaJIT, most of the performance advantages
>> disappear when you do this.
>
> However, even with the JIT disabled, LuaJIT does tend to outperform
> Lua for a lot of use cases (Lua wins in a few cases) just by virtue of
> having an interpreter written in hand-tuned assembly.
>
> /s/ Adam

Addendum: FFI still works on iOS at least, and probably WinRT.

/s/ Adam


  reply	other threads:[~2014-01-14 20:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  1:25 Jason
     [not found] ` <CAF7MipWEwTYp2UJO8-kNoVDEK0mPCQFBay7pYeCZTrqKYevx6g@mail.gmail.com>
     [not found]   ` <CAHmME9pAXcyxypr0ogh4Or1DR-NBcyxDMed0m9uyu=6h=uRt5Q@mail.gmail.com>
2014-01-14  2:16     ` Jason
2014-01-14 19:53       ` fw
     [not found] ` <B0F514CB-B748-48EA-B771-D557DEA82913@gmail.com>
2014-01-14  2:22   ` Jason
2014-01-14  2:37     ` andrew.starks
2014-01-14  2:51       ` Jason
2014-01-14  3:17         ` andrew.starks
2014-01-14  3:51         ` andrew.starks
2014-01-14  8:09           ` justin
2014-01-14 13:03           ` Jason
     [not found] ` <20140114023403.GA31401@wilbur.25thandClement.com>
2014-01-14  2:45   ` Jason
2014-01-14 20:41 ` ewmailing
2014-01-14 20:50   ` chighland
2014-01-14 20:50     ` chighland [this message]
2014-01-15  1:32       ` malkia

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='CAFE_sBGWtjk-qRAHQGLNyjYJEfiswno1zWqkWFz50axCgsSN=A@mail.gmail.com' \
    --to=cgit@lists.zx2c4.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).