Re: Use define_constraint for MIPS

[Zack Weinberg <zackw at panix dot com>]

On Fri, Mar 10, 2006 at 07:10:42AM +0000, Richard Sandiford wrote:
> Zack Weinberg <zackw@panix.com> writes:
> >
> > The latter.  Note that my plan is to have "@internal" constraints show
> > up in the internals manual, but not the user manual.
> 
> Ah, OK.  To be honest, I don't see the point of having _any_ machine-specific
> constraints in the internals manual once a machine have been converted to
> use define_constraint.  I suppose one of the reasons for having them in
> the old days was because the definitions were split over so many macros,
> and having a centralised list in the internals manual might have been
> useful.  But now we can simply say "Each machine can also define extra
> constraints in its constraints.md file.  See ... for the format of the
> constraint definitions."

Well, I kinda liked the idea of a 100% comprehensive list in the internals
manual, but if you don't think it would be useful, I will cheerfully
defer to the person who has, y'know, actually written a back end. :)

Mind correcting the discussion of (future) docstring handling in the
how-to-define-constraints section of the manual?

Also, I'm in pre-final-exams crunch and won't have time to mess with
gcc until next month, so if you feel like making i386 a constraints.md
please go ahead.

zw