Skip to content

V8 will remove the MIPS(64) port #26179

Closed

Description

@natorion

This is in the context of https://groups.google.com/forum/#!topic/v8-dev/oXkv5OVCXyc.

As nobody stepped up to maintain the ports, V8's current plan is to remove the MIPS(64) ports from the V8 codebase with V8 7.5 (~ mid March 2019).

As MIPS(64) is also not supported in Node.js (https://github.com/nodejs/node/blob/master/BUILDING.md#supported-platforms-1), I don't know if this is really relevant to you folks at all? Please speak up if this is not the case.

Activity

  1. natorion commented on Feb 18, 2019

    @natorion
    Author
  2. added
    v8 engineIssues and PRs related to the V8 dependency.
    mipsIssues and PRs related to the MIPS architecture.
    on Feb 18, 2019
  3. hashseed commented on Feb 18, 2019

    @hashseed
    Member

    Note that the MIPS port has already been broken for a while.

  4. added a commit that references this issue on Feb 18, 2019
  5. added
    buildIssues and PRs related to Node.js builds or CI infrastructure.
    on Feb 18, 2019
  6. richardlau commented on Feb 18, 2019

    @richardlau
    Member

    FYI @nodejs/distros

  7. bnoordhuis commented on Feb 18, 2019

    @bnoordhuis
    Member

    I did see the announcement but thanks for the reminder. :-)

    We don't claim to support mips(64)(el) or test it regularly so I think it's just a matter of dropping it from the build scripts: #26192

  8. refack commented on Feb 18, 2019

    @refack
    Contributor

    I actually have node@8 running in OpenWRT on a TP-Link Archer C7 (CPU is a Qualcomm Atheros QCA9558) patched using https://github.com/openwrt/packages/tree/master/lang/node.
    But AFAIK even node 9 and 10 were never properly ported.

  9. richardlau commented on Feb 18, 2019

    @richardlau
    Member

    Also cc @kapouer based on previous issues raised re. MIPS.

  10. glaubitz commented on Feb 19, 2019

    @glaubitz

    One of the problems here is that Firefox currently has a hard build dependency on nodejs, so distributions will no longer be able to build Firefox. On the other hand, it would be possible to perform the Firefox build steps which require nodejs on an x86_64 machine and then include these build artifacts in the MIPS builds.

  11. hashseed commented on Feb 19, 2019

    @hashseed
    Member

    One of the problems here is that Firefox currently has a hard build dependency on nodejs, so distributions will no longer be able to build Firefox. On the other hand, it would be possible to perform the Firefox build steps which require nodejs on an x86_64 machine and then include these build artifacts in the MIPS builds.

    I think that would be preferable. Do you have the option to cross-compile?

  12. nxhack commented on Feb 20, 2019

    @nxhack

    @refack
    I ported v10.x v11.x to openwrt. The build is going well (mips, mipsel).

    https://github.com/nxhack/openwrt-node-packages/tree/master/node

  13. natorion commented on Feb 22, 2019

    @natorion
    Author

    FYI, it currently looks like another company is stepping up to maintain the MIPS(64) port modulo Big Endian. I will keep you posted.

  14. rwaldron commented on Feb 25, 2019

    @rwaldron

    @natorion link or reference? Thanks in advance.

  15. natorion commented on Feb 26, 2019

    @natorion
    Author
  16. axetroy commented on Apr 26, 2021

    @axetroy

    Currently under active maintenance is loongson CPU. They use mips architecture and the company is well-funded.

    A large number of orders have been obtained, and there will be a lot of mips demand in the next few years (in China)

    http://www.loongson.cn/product/cpu/

  17. added a commit that references this issue on Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to Node.js builds or CI infrastructure.mipsIssues and PRs related to the MIPS architecture.v8 engineIssues and PRs related to the V8 dependency.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions