Sorry, the mozilla-esr24 code is at:
        https://github.com/loongsonhf/loongson-mozilla-central

在 2014年2月19日星期三UTC+8下午3时00分41秒,[email protected]写道:
> Hi all,
> 
> 
> 
> We are IonMonkey development team from Loongson Inc, China. We have been
> 
> ported IonMonkey of Mozilla-esr24 to our Loongson 3A  MIPS platform, which is
> 
> available at github:
> 
>         https://github.com/loongsonhf/loongson-mozilla-central
> 
> This job is finished, and IonMonkey works well at our Loongson 3A platform.
> 
> 
> 
> Now we are porting IonMonkey to Loongson 3A on the latest mozilla-central
> 
> code. The code is available at:
> 
>         https://github.com/loongsonhf/loongson-mozilla-central
> 
> There are some bugs now, with 99% baseline and ion test cases passed,  
> 
> we are trying to solve as soon as possible.
> 
> 
> 
> We planed to submit our code to Mozilla last year(Dec, 2013), and emailed to
> 
> to Jan de Mooij about this. As Petar, Paul and Branislav from Imgtec began to
> 
> submit patch at Mozilla's bugzilla, we think there can be a way to collaborate
> 
> to accomplish this work.
> 
> 
> 
> Regards,
> 
> Weizhenwei
> 
> 
> 
> 
> 
> 在 2014年2月7日星期五UTC+8下午5时18分57秒,Jan de Mooij写道:
> 
> > Hi,
> 
> > 
> 
> > 
> 
> > 
> 
> > There's a (Chinese) company working on MIPS support as well. Are they
> 
> > 
> 
> > related to you in any way? If not, hopefully you will be able to
> 
> > 
> 
> > collaborate; I sent them a link to this thread so that they can
> 
> > 
> 
> > contact you.
> 
> > 
> 
> > 
> 
> > 
> 
> > On Thu, Feb 6, 2014 at 10:36 PM, Branislav Rankov
> 
> > 
> 
> > <[email protected]> wrote:
> 
> > 
> 
> > > 1. Would you like to review the code while on GitHub, or only trough the
> 
> > 
> 
> > > patches submitted to Bugzilla?
> 
> > 
> 
> > 
> 
> > 
> 
> > Some of our teams use GitHub but we don't use it for
> 
> > 
> 
> > Gecko/SpiderMonkey development, so Bugzilla would be easier for us.
> 
> > 
> 
> > 
> 
> > 
> 
> > > 2. How large should the individual patches be?
> 
> > 
> 
> > 
> 
> > 
> 
> > As small as possible. It's usually easier to review many small patches
> 
> > 
> 
> > than 1 big patch.
> 
> > 
> 
> > 
> 
> > 
> 
> > > 3. How often should the patches be submitted? I guess this depends on
> 
> > 
> 
> > > reviewer availability.
> 
> > 
> 
> > >
> 
> > 
> 
> > > My current plan is to submit the code in 5 phases:
> 
> > 
> 
> > > - Skeleton code and Assembler
> 
> > 
> 
> > > - Baseline Compiler code
> 
> > 
> 
> > > - IonMonkey code
> 
> > 
> 
> > > - OdinMonkey code
> 
> > 
> 
> > > - MIPS simulator
> 
> > 
> 
> > 
> 
> > 
> 
> > That's a reasonable plan I think and is definitely better than landing
> 
> > 
> 
> > it all at once.
> 
> > 
> 
> > 
> 
> > 
> 
> > > I can separate assembly parts from integration parts if you wish.
> 
> > 
> 
> > 
> 
> > 
> 
> > That would be nice. I expect the assembly part to be pretty big, maybe
> 
> > 
> 
> > Andreas or Brendan can review that and one of us can review the
> 
> > 
> 
> > changes to the rest of the engine/JITs?
> 
> > 
> 
> > 
> 
> > 
> 
> > > I will follow the discussions here and will be available on #jsapi on IRC
> 
> > 
> 
> > > during Europe daytime. My IRC nick is rankov.
> 
> > 
> 
> > 
> 
> > 
> 
> > Great, thanks.
> 
> > 
> 
> > 
> 
> > 
> 
> > Jan
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals

Reply via email to