lukechilds
/
node
mirror of https://github.com/lukechilds/node.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
13045 Commits
131 Branches
446 Tags
325 MiB
 
 
 
 
 
 
Tree: 2c97bd47e4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2c97bd47e4'
${ noResults }
node/deps/v8/docs/handling_of_ports.md

869 B
Raw Blame History

General

This article describes how ports should be handled.

MIPS

Straight-forward MIPS ports

  1. Do them yourself.

More complicated MIPS ports

  1. CC the MIPS team in the CL. Use the mailing list v8-mips-ports.at.googlegroups.com for that purpose.
  2. The MIPS team will provide you with a patch which you need to merge into your CL.
  3. Then land the CL.

PPC (not officially supported)

  1. Contact/CC the PPC team in the CL if needed. Use the mailing list v8-ppc-ports.at.googlegroups.com for that purpose.

x87 (not officially supported)

  1. Contact/CC the x87 team in the CL if needed. Use the mailing list v8-x87-ports.at.googlegroups.com for that purpose.

ARM

Straight-forward ARM ports

  1. Do them yourself.

When you are lost

  1. CC the ARM team in the CL. Use the mailing list v8-arm-ports.at.googlegroups.com for that purpose.