Looking for people to maintain the MIPS port

[Michael Hablich]

Hi,

we thank RT-RK and Wave Computing for the yearlong work on V8's MIPS port. Unfortunately Wave Computing is no longer sponsoring V8's MIPS port, thus RT-RK cannot continue working on it.

This means that we are now looking for entities that are willing to maintain the port instead. If you are interested, please get in touch with me.

It would also be good to know if your usage of V8 is reliant on the MIPS port.

Cheers,

Michael

[Michael Hablich]

Hi,

there was no response to this thread and other outreach at all, so we will go ahead and remove the MIPS(64) ports from V8 starting with V8 7.5 (~mid March).

Cheers,

Michael

+v8-mips-ports 

[xwa...@gmail.com]

Hi, I am working for Loongson technology company in China, loongson design and produce many series mips CPU, we have many customers, and we need chromium & nodejs. RT-RK and Wave Computing maintain the mips port very well before, so we did not do much work about v8.

so we want maintain the mips port now, I had do some work about port v8 to mips64 with Paul in 2014, after that I did not do any more about v8 mips.
https://chromium-review.googlesource.com/c/v8/v8/+/1369908
this is my last patch but it is not reviewed.

Thank you.

[pfge...@gmail.com]

Hi Michael
We just saw this message because of the Spring Festival. I am in charge of browser development in Loongson technology. In the past, we have done a lot of work based on chromium and V8 for our customers and contributed a lot of code in these communities. Our company is willing to invest more resources to maintain the MIPS branch, including V8 and chromium. My colleague YuYin（xwa...@gmail.com） and I are willing to become maintainers of the V8 MIPS branch. We hope that the MIPS branch of V8 will not be removed from the main branch.

Thanks
fei

[Michael Hablich]

Hi folks,

thanks for you message! I propose to discuss this offline to this thread. Can you please send me a mail with more details to hab...@chromium.org?

Cheers,

Michael

[pfge...@gmail.com]

Hi Michael
Mail has been sent to you. Please check it.

Thanks
fei

[Michael Hablich]

Hi,

it currently looks like another company is stepping up to maintain the MIPS (64) ports modulo Big Endian. I will keep this thread updated, when details are hashed out.

Cheers,

Michael

[Michael Hablich]

Hi,

great news! Loongson (on CC) is indeed willing and ready to maintain V8's MIPS ports, not including Big Endian though. Thanks! Next steps:

1.) Add Loongson people to v8-mip...@googlegroups.com

2.) Remove Big Endian bot from https://ci.chromium.org/p/v8/g/ports/console

3.) Make the MIPS port green again.

Cheers,

Michael

On Fri, Feb 22, 2019 at 9:01 AM Michael Hablich <hab...@chromium.org> wrote:

Hi,

it currently looks like another company is stepping up to maintain the MIPS (64) ports modulo Big Endian. I will keep this thread updated, when details are hashed out.

Cheers,

Michael

On Monday, February 18, 2019 at 10:23:34 AM UTC+1, Michael Hablich wrote:

Hi,

there was no response to this thread and other outreach at all, so we will go ahead and remove the MIPS(64) ports from V8 starting with V8 7.5 (~mid March).

Cheers,

Michael

+v8-mips-ports 

On Mon, Feb 4, 2019 at 11:30 AM Michael Hablich <hab...@chromium.org> wrote:

Hi,

we thank RT-RK and Wave Computing for the yearlong work on V8's MIPS port. Unfortunately Wave Computing is no longer sponsoring V8's MIPS port, thus RT-RK cannot continue working on it.

This means that we are now looking for entities that are willing to maintain the port instead. If you are interested, please get in touch with me.

It would also be good to know if your usage of V8 is reliant on the MIPS port.

Cheers,

Michael

--
--
v8-dev mailing list
v8-...@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to a topic in the Google Groups "v8-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/v8-dev/oXkv5OVCXyc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to v8-dev+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Refael Ackermann]

BTW The Node.js Build WG would also appreciate any possible help with implementing CI for MIPS.

Feel free to contact me directly.

[Ben Noordhuis]

On Tue, Feb 26, 2019 at 12:34 PM Michael Hablich <hab...@chromium.org> wrote:
> great news! Loongson (on CC) is indeed willing and ready to maintain V8's MIPS ports, not including Big Endian though. Thanks!

For my understanding, that means mipsel and mipsel64 but no more mips
and mips64?

[yuyin QQ]

yes

在 2019年2月27日星期三 UTC+8上午3:33:27，Ben Noordhuis写道：

[yuyin QQ]

hi

very sorry for the late reply.

I'd like to do something if need about  implementing nodejs CI for MIPS.

I just have a test about nodejs 10.15.3, it need do some change about build file and then work fine for me.

I also notice that openssl need architecture-related asm code which mips does not support yes, we will try to support it soon.

Thank you.

在 2019年2月26日星期二 UTC+8下午11:22:32，Refael Ackermann写道：

[whh...@gmail.com]

Hi yuyin:

 I just build nod...@12.14.0 on mips64el (loongson 3A3000)  with --with-snapshot ，the result was successed. When I run nodejs, it crashed. The messages are as follows:

#

# Fatal error in ../deps/v8/src/execution/isolate.cc, line 232

# Embedded blob checksum verification failed. This indicates that the embedded blob has been modified since compilation time. A common cause is a debugging breakpoint set within builtin code.

#

#

#

#FailureMessage Object: 0xffffffacc0

Program received signal SIGTRAP, Trace/breakpoint trap.

v8::base::OS::Abort () at ../deps/v8/src/base/platform/platform-posix.cc:406

But nodejs@v10.x and nodejs@v11.x works fine. I found that when I build nodejs@v12.x with `--without-snapshot`，then nodejs works fine. Maybe mips64el has some problems with v8 snapshot. 

The versions of v8 and nodejs are :

1. nod...@12.14.0 -> v...@7.7.299.13
2. nod...@11.15.1 -> v...@7.0.276.38
3. nod...@10.17.0 -> v...@6.8.275.32

Looking Forward to Hearing From You.

在 2019年5月8日星期三 UTC+8上午9:36:08，yuyin QQ写道：

[Ben Noordhuis]

On Tue, Dec 24, 2019 at 11:46 AM <whh...@gmail.com> wrote:
>
> Hi yuyin:
>
> I just build nod...@12.14.0 on mips64el (loongson 3A3000) with --with-snapshot ，the result was successed. When I run nodejs, it crashed. The messages are as follows:
>
> #
> # Fatal error in ../deps/v8/src/execution/isolate.cc, line 232
> # Embedded blob checksum verification failed. This indicates that the embedded blob has been modified since compilation time. A common cause is a debugging breakpoint set within builtin code.
> #
> #
> #
> #FailureMessage Object: 0xffffffacc0
> Program received signal SIGTRAP, Trace/breakpoint trap.
> v8::base::OS::Abort () at ../deps/v8/src/base/platform/platform-posix.cc:406
>
>
> But nodejs@v10.x and nodejs@v11.x works fine. I found that when I build nodejs@v12.x with `--without-snapshot`，then nodejs works fine. Maybe mips64el has some problems with v8 snapshot.
>
> The versions of v8 and nodejs are :
>
> nod...@12.14.0 -> v...@7.7.299.13
> nod...@11.15.1 -> v...@7.0.276.38
> nod...@10.17.0 -> v...@6.8.275.32
>
> Looking Forward to Hearing From You.

It's possible your issue is caused by the way Node.js builds V8 rather
than something intrinsic to V8. Can you open an issue over at
https://github.com/nodejs/node/issues and cc me (@bnoordhuis)? Can you
also test Node.js v13.5.0?

Expectation management: mips(el) is not an officially supported
architecture, it's self-serve, but I'll try to help you out. :-)