From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2933 invoked by alias); 6 Dec 2010 20:30:48 -0000 Received: (qmail 2925 invoked by uid 22791); 6 Dec 2010 20:30:47 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 06 Dec 2010 20:30:43 +0000 Received: (qmail 4699 invoked from network); 6 Dec 2010 20:30:41 -0000 Received: from unknown (HELO digraph.polyomino.org.uk) (joseph@127.0.0.2) by mail.codesourcery.com with ESMTPA; 6 Dec 2010 20:30:41 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.72) (envelope-from ) id 1PPhho-0000Jp-C8; Mon, 06 Dec 2010 20:30:40 +0000 Date: Mon, 06 Dec 2010 20:34:00 -0000 From: "Joseph S. Myers" To: Eric Botcazou cc: Yao Qi , gcc-patches@gcc.gnu.org Subject: Re: [Ping] [patch 0/3] New macro PREFERRED_RENAME_CLASS In-Reply-To: <201012061925.26662.ebotcazou@adacore.com> Message-ID: References: <4CD24091.1020904@codesourcery.com> <201012031157.20334.ebotcazou@adacore.com> <4CF8F991.4080304@codesourcery.com> <201012061925.26662.ebotcazou@adacore.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2010-12/txt/msg00511.txt.bz2 On Mon, 6 Dec 2010, Eric Botcazou wrote: > --- a/gcc/doc/tm.texi.in > +++ b/gcc/doc/tm.texi.in > @@ -2496,6 +2496,8 @@ looking for one that is valid, and will reload one or > both registers > only if neither labeling works. > @end defmac > > +@hook TARGET_PREFERRED_RENAME_CLASS > + > @hook TARGET_PREFERRED_RELOAD_CLASS > A target hook that places additional restrictions on the register class > to use when it is necessary to copy value @var{x} into a register in class > > It looks like most of the hooks have some text in tm.texi.in so I'd suggest > writing a single sentence in target.def and move the rest of the text (with > the example) to tm.texi.in. No! Never do that for a new hook. That should only ever be done if the hook documentation is based on pre-existing GFDL-only text, while we are waiting for the FSF Board of Directors to resolve the problems with not being able to move text from one place to another. target.def is always the preferred place for hook documentation where legally possible. -- Joseph S. Myers joseph@codesourcery.com