[patch/rfc] Moving constraint definitions to the machine description

[Joseph S. Myers]

On Sat, 7 Jan 2006, Zack Weinberg wrote:

> and IOR expressions).  It allows us to generate the "machine-specific
> constraints" section of the manual from the machine descriptions,
> eliminating skew between the manual and the source code.  The

At this point I think we'll need to move update_web_docs_svn to 
configuring and running "make info-gcc" to build all the generated .texi 
files rather than adding to the local rules there for building manuals; 
with the current gcc.gnu.org machine this shouldn't cause load problems.  
(Then the question applies of which sources to include in the source 
tarball, but we can always include the .md files in there, moving the 
deletion of unwanted sources to after the .texi files are built.)  (There 
will be consequential changes to sourcebuild.texi from the addition of 
this doc generation - documentation will no longer need adding to md.texi 
for new ports and generated .texi files need not be checked in.)

-- 
Joseph S. Myers               http://www.srcf.ucam.org/~jsm28/gcc/
    jsm@polyomino.org.uk (personal mail)
    joseph@codesourcery.com (CodeSourcery mail)
    jsm28@gcc.gnu.org (Bugzilla assignments and CCs)