Re: RISC OS Javascript support

Hi Chris, thanks for your ongoing help with this.

On Sat, Dec 15, 2012 at 01:53:03PM +0000, Chris Gransden wrote:
> In article <20121214122314.GG15360@kyllikki.org>,
> Vincent Sanders <vince@netsurf-browser.org> wrote:
> > Thankyou for all your feedback.
>
> > As some of you discovered there was no user interface to enable
> > javascript so you would need to add:
>
> > enable_javascript:1
>
> > to your configuration manually.
>
> While testing the various spidermonkey versions I added the user interface
> to enable javascript. Here's a screen dump www.cgransden.co.uk/screen.png.

Please can you send a patch? even if its just the files you changed I
can work up a suitable patch from those, whatevers easiest.

>
> > It seems that the RISC OS edition of spidermonkey is failing to even
> > initialise as can be seen within the log as:
>
> > javascript/jsapi.c js_initialise 39: New runtime handle 0x0
>
> With 1.85 on RISC OS this happens with the JIT turned on. If the JIT is
> disabled it gets a bit further then gets stuck in a loop.

How do we disable JIT? I used your recipie to build spidermonkey as a
template. Even with --disable-tracejit passed to configure METHOD JIT
is still enabled (toolchain build has the patches and Makefile used[1]
(in the sdk directory)). If I turn that off too (--disable-methodjit)
the library fails to build, perhaps I am missing something?

I would like to try and debug where the later version of spidermonkey
fails as it is such a huge improvement in functionality going
forwards.

>
> > which effectively means the javascript support is disabled and will not
> > be able to use any script code on this platform (many of your examples
> > work fine on the Linux platforms being used for development).
>
> > If time permits I may look into this further but as I have limited
> > access to RISC OS systems myself and the platform maintainer is
> > currently not active I cannot promise progress in the immediate
> > future.
>
> > Sorry this was not more useful at this time but I do feel progress is
> > being made albeit slowly.
>
> Would it be an option to use Spidermonkey 1.7 on RISC OS temporarily? This
> version seems stable and all the javascript tests work ok. They give the
> same results as the gtk version which uses 1.85.

I can build 1.7 temporarily, but this is not really solving the issue
at all and will (from past experience) almost certianly lead to RISC
OS being stuck there forever.

In future I do wish to move onto editions of spidermonkey past 1.8.5
(3 years old) which provide improved perfomance and functionality so
limiting myself to version 1.7 (which is over five years old now, think
firefox 2 era) seems counterproductive.

>
> Chris.
>
>
>

[1] http://git.netsurf-browser.org/toolchains.git/tree/


--
Regards Vincent
http://www.kyllikki.org/