On Thursday, February 6, 2014 7:36:39 PM UTC+1, Brendan Eich wrote: > Jan de Mooij wrote: > > > OnThu, Feb 6, 2014 at 6:35 PM, Nicolas B. Pierron > > > <[email protected]> wrote: > > >> > As they are looking at making a working mobile device, I recommended > >> > that > > >> > they also add a MIPS Simulator (which would be added to v8 soon). The > >> > MIPS > > >> > Simulator will serve 2 purposes: > > >> > - Check the MIPS backend on Try. > > >> > - Make MIPS testing easier for other devs. > > > > > > The problem I see with this is that MIPS is a tier-3 platform afaik > > > and we don't have real MIPS hardware to test on. So what do we do when > > > we break the MIPS simulator build? What if we add a new feature that > > > requires MIPS assembler + simulator changes, something similar to the > > > float32 work that happened? We can do our best to apply > > > changes/refactorings etc also to the MIPS directory, but I don't think > > > we can keep MIPS working at all cost with no way to test it... > > > > It'd be up to the MIPS back end initial contributors and anyone else > > interested to carry the cost. Tier-3 means we can break it, of course we > > should avoid trivially avoidable breakage, but still. > > > > If no one else offers, I'll read MIPS assembly bit. I <3 MIPS. > > > > /be
As of a platform to test it on, QEMU can be an option and we can also help in terms of hardware if needed. As of MIPS backend changes, we do plan ongoing support here, same what we do for v8 for the last few years. Regards, Petar _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
