Received: by 10.90.2.18 with SMTP id 18mr2670980agb.15.1301726416618;
        Fri, 01 Apr 2011 23:40:16 -0700 (PDT)
X-BeenThere: v8-users@googlegroups.com
Received: by 10.91.44.8 with SMTP id w8ls864160agj.5.p; Fri, 01 Apr 2011
 23:40:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.90.24.36 with SMTP id 36mr886051agx.51.1301726414214; Fri, 01
 Apr 2011 23:40:14 -0700 (PDT)
Received: by k3g2000prl.googlegroups.com with HTTP; Fri, 1 Apr 2011 23:40:14
 -0700 (PDT)
Date: Fri, 1 Apr 2011 23:40:14 -0700 (PDT)
In-Reply-To: <AANLkTi=6aOc5zpySeaVT2QS5zPUHB52oonTM5mLEyNT4@mail.gmail.com>
X-IP: 210.94.41.89
References: <a54dc73c-14f8-421e-aece-b25f1e64b23c@u3g2000vbe.googlegroups.com>
 <AANLkTikoD5F5AKWhzZcLf71LgncWWJFQHDu2ofmj3MhH@mail.gmail.com>
 <AANLkTimTaweTzA_kE2r8EcxO=VYUpFAfJ_bbfQnhp2h5@mail.gmail.com>
 <0835b752-58e0-45e3-837a-baebecc31d26@dn9g2000vbb.googlegroups.com> <AANLkTi=6aOc5zpySeaVT2QS5zPUHB52oonTM5mLEyNT4@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-Via: 1.1 Samsung_proxy10:8080 (DataReactor/4.0.6)
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
 AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16,gzip(gfe)
Message-ID: <d24fb256-5472-4297-8c38-666d59b3c301@k3g2000prl.googlegroups.com>
Subject: Re: ARM support - which architecture variants?
From: Arun M <arunm.chr...@gmail.com>
To: v8-users <v8-users@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Hi

Is Crankshaft optimizing compiler enabled for ARMv7-A + NEON devices
which does not have VFPv3 FPU?

Thanks & Regards
Arun


On Mar 9, 6:02=A0pm, S=F8ren Gjesse <sgje...@chromium.org> wrote:
> For ARM crankshaft is now the default. This change is in the repository
> starting from V8 version 3.2. To use the previous optimizing compiler
> --nocrankshaft will have to be used. When crankshaft for ARM has been ful=
ly
> stabilized the previous optimizing compiler will be removed from the
> repository and running with --nocrankshaft will no longer be possible. Th=
ere
> is no specific date to when this will happen but most likely it will be
> within a month or two. The removal of the previous optimizing compiler wi=
ll
> happen for all supported platforms simultaneously,
>
> The previous optimizing compiler can of cause still be found in previous
> versions of V8.
>
> Regards,
> S=F8ren
>
>
>
>
>
>
>
> On Tue, Mar 8, 2011 at 20:05, Hugo Vincent <hugo.vinc...@gmail.com> wrote=
:
> > How much slower is full-compiler than nocrankshaft on ARM926ej-s -
> > anyone have any benchmarks? I'm hesitant to invest time in using V8
> > for my project if it's going to get substantially slower soon. Is
> > there any estimated time frame for when nocrankshaft will be
> > deprecated?
>
> > Thanks,
> > Hugo
>
> > On Feb 23, 9:14 pm, S=F8ren Gjesse <sgje...@chromium.org> wrote:
> > > Just a follow-up note regarding the new optimizing compiler (cranksha=
ft).
> > > This will be enabled by default for ARM quite soon, and the existing
> > > optimizing compiler will be removed at some point. For non ARMv7+VFP
> > devices
> > > this means that the base JIT (non-optimizing/full-compiler) will be u=
sed.
> > To
> > > measure the different compilers on a ARMv7+VFP device use following
> > options:
>
> > > =A0 --nocrankshaft (current optimizing JIT - the current default)
> > > =A0 --crankshaft (new optimizing JIT - the soon to be default)
> > > =A0 --always-full-compiler (base/non-optimizing compiler)
>
> > > Going forward using --crankshaft on a non ARMv7+VFP device will have =
no
> > > effect and execution will fallback to --always-full-compiler.
>
> > > Regards,
> > > S=F8ren
>
> > > On Wed, Feb 23, 2011 at 18:33, Rodolph Perfetta
> > > <rodolph.perfe...@gmail.com>wrote:
>
> > > > V8 can run on ARMv4 devices (non T though).
>
> > > > There is no interpreter in V8 so you will be using the JIT every ti=
me,
> > > > perfromance should be good (keep in mind CPU like 926-ej-s do not h=
ave
> > L2
> > > > cache and this is going to have a visible impact). There is a new J=
IT
> > > > infrastructure being developed (crankshaft) which features an
> > optimising JIT
> > > > and this will only be for ARMv7+VFP devices.
>
> > > > HTH,
> > > > Rodolph.
>
> > > > On 23 February 2011 17:12, Hugo Vincent <hugo.vinc...@gmail.com>
> > wrote:
>
> > > >> Hi,
>
> > > >> I can't find in the documentation which ARM architecture types V8
> > > >> supports. Does it support older ARM9 devices (I'm specifically
> > > >> interested in an ARMv5te architecture, ARM926ej-s device) or only
> > > >> newer ARMv7 (Cortex-A8 etc)? I can see that it is (supposed to) bu=
ild
> > > >> on ARMv5te, but do all the JIT features work or is it running in a
> > > >> byte code interpreter fallback or something? Can I expect good
> > > >> performance?
>
> > > >> Thanks,
> > > >> Hugo
>
> > > >> --
> > > >> v8-users mailing list
> > > >> v8-users@googlegroups.com
> > > >>http://groups.google.com/group/v8-users
>
> > > > =A0--
> > > > v8-users mailing list
> > > > v8-users@googlegroups.com
> > > >http://groups.google.com/group/v8-users
>
> > --
> > v8-users mailing list
> > v8-users@googlegroups.com