I should ask the following general standard new-port questions: * Does the port build cleanly when configured with --enable-werror-always and built using a native compiler from current GCC trunk - for both 32-bit host, and 64-bit host? It should. This is the standard way of ensuring the same level of warning-cleanness in a cross build as native bootstrap automatically enforces (and the build compiler needs to be from current trunk because warning-cleanness is only expected when the build compiler is the same version as the compiler being built).
The new targets should be added to contrib/config-list.mk, which helps test all targets with --enable-werror-always. This is mentioned in "Back End" in sourcebuild.texi - check there for any other pieces that should be included in the port submission. * What are test results like for the port? Again, both 32-bit and 64-bit hosts, to detect any dependencies on whether the host is 32-bit or 64-bit. -- Joseph S. Myers jos...@codesourcery.com
