From: "Joseph S. Myers" <joseph@codesourcery.com>
To: gcc-patches@gcc.gnu.org
Cc: Bernd Schmidt <bernds@codesourcery.com>,
Joern Rennecke <joern.rennecke@embecosm.com>
Subject: Mention config-list.mk in new port checklist
Date: Tue, 10 May 2011 15:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1105101533490.6103@digraph.polyomino.org.uk> (raw)
I noticed that contrib/config-list.mk was missing from the new-port
checklist in doc/sourcebuild.texi. I've applied this patch to add it;
target triplets covering all config.gcc stanzas for a new port should be
added to config-list.mk so the port gets covered in all-targets build
tests (and, of course, it should be tested that a new port does actually
pass "make all-gcc" with --enable-werror-always using a current native
trunk compiler to build it - ideally this should be tested for both 32-bit
and 64-bit hosts).
Index: ChangeLog
===================================================================
--- ChangeLog (revision 173620)
+++ ChangeLog (working copy)
@@ -1,5 +1,9 @@
2011-05-10 Joseph Myers <joseph@codesourcery.com>
+ * doc/sourcebuild.texi (Back End): Mention contrib/config-list.mk.
+
+2011-05-10 Joseph Myers <joseph@codesourcery.com>
+
* config/rs6000/genopt.sh, config/rs6000/rs6000-cpus.def: New
files.
* config/rs6000/rs6000-tables.opt: New file (generated).
Index: doc/sourcebuild.texi
===================================================================
--- doc/sourcebuild.texi (revision 173620)
+++ doc/sourcebuild.texi (working copy)
@@ -834,6 +834,9 @@
@file{MAINTAINERS}. Some existing architectures may be unmaintained,
but it would be unusual to add support for a target that does not have
a maintainer when support is added.
+@item
+Target triplets covering all @file{config.gcc} stanzas for the target,
+in the list in @file{contrib/config-list.mk}.
@end itemize
@node Testsuites
--
Joseph S. Myers
joseph@codesourcery.com
reply other threads:[~2011-05-10 15:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.1105101533490.6103@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joern.rennecke@embecosm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).