List for cgit developers and users
 help / color / mirror / Atom feed
From: fw at deneb.enyo.de (Florian Weimer)
Subject: cgit-lua: to jit or not to jit
Date: Tue, 14 Jan 2014 20:53:23 +0100	[thread overview]
Message-ID: <87lhyijq6k.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CAHmME9qh==YTUwAg0=yAcUcSqrT7jSfzOQCUjfAR_vsYdiD0Rw@mail.gmail.com> (Jason A. Donenfeld's message of "Tue, 14 Jan 2014 03:16:33 +0100")

* Jason A. Donenfeld:

> On Tue, Jan 14, 2014 at 3:10 AM, demetri <demetri.spanos at gmail.com> wrote:
>> 1) PUC Lua works on more machines/architectures (though Mike has
>> substantially closed the gap for most architectures people care about in a
>> non-embedded non-mobile environment)
>
> Do you know what the gap is?
>
> LuaJIT supports x86, x86_x64, arm, ppc, e500, and mips. I guess that
> leaves, what? Sparc, AVR, ia64, ... other obscure ones? Hmm..

ppc64 and s390x.  Neither one is particularly obscure.


  reply	other threads:[~2014-01-14 19:53 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 [this message]
     [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
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=87lhyijq6k.fsf@mid.deneb.enyo.de \
    --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).