We are currently using uClibC, it works well for all the system we
have (glib + protocol buffer + mplayer + ...).

We compile V8, it almost work. But Math.random() returns
"8.263547083e-315" and the strange issue for the date.

I cannot find if it comes from V8 or uClibC.

I've tried unsuccessfully to use a standard libC in our environment
but it a to complex modification in our system.

Do you have any idea ?

Best regards.
Julien.

On Nov 26, 1:29 pm, Rodolph Perfetta <[email protected]>
wrote:
> Hi,
>
> I couldn't reproduce your issue, an armv4 build of bleeding_edge gives me
> the right result.
>
> Are the C libraries on your platform working properly? Could you try and
> narrow it down a bit: is it Math.floor or Math.random (or both) which is an
> issue?
>
> Cheers,
> Rodolph.
>
> On 25 November 2010 14:09, JulienC <[email protected]> wrote:
>
>
>
>
>
>
>
> > Hi all,
>
> > I currently encounter 2 issues with V8 on armV4 (arm920t), I don't
> > know if they are related or not.
>
> > The first is with Math.random() when I try to get a number in 0-9,
>
> > on my mac, it works well:
> >  >Math.floor(Math.random()*10)
> >  2
>
> > on armV4, strange behaviour:
> >  >Math.floor(Math.random()*10)
> >  1.6427083566e-314
>
> > I'm using the trunk but it seems to do the same for all versions.
>
> > The second issue is concerning the Date object, when I try to set a
> > date, it always return 01/01/1970...
>
> > on my mac:
> >  > new Date()
> >  Thu Nov 25 2010 14:59:26 GMT+0100 (CET)
> >  > new Date(2009, 11, 30)
> >  Wed Dec 30 2009 00:00:00 GMT+0100 (CET)
>
> > on armV4:
> >  > new Date()
> >  Thu Nov 25 2010 00:00:00 GMT+0000 (UTC)          //no time ?
> >  > new Date(2009, 11, 30)
> >  Thu Jan 01 1970 00:00:00 GMT+0000 (UTC)          // wrong date !
>
> > I hope that someone has any idea about one of those issues.
>
> > Best regards.
>
> > --
> > v8-users mailing list
> > [email protected]
> >http://groups.google.com/group/v8-users

-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users

Reply via email to