| # 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. |
| 1. The MIPS team will provide you with a patch which you need to merge into your CL. |
| 1. Then land the CL. |
| |
| If for an important reason the MIPS patch cannot be included in your CL and you need to land your change immediately, then: |
| * Disable the test that fail on MIPS in your CL |
| * File a separate backport bug, reference it in your CL description, and state on the bug which tests need to be re-enabled in the backport CL. |
| * Review the backport CL and ensure tests get re-enabled in the backport CL (which should also reference the backport bug). |
| |
| # 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. |
| |
| # s390 (not officially supported) |
| 1. Contact/CC the s390 team in the CL if needed. Use the mailing list v8-s390-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. |