Ada patches

[Arnaud Charlet <charlet at ACT-Europe dot FR>]

You may have noticed that my recent Ada patches have a rather different
style than in the past. This reflects some changes in internal procedures
we are making so that the patches we submit are easier to read and
understand, and should be significantly easier for other gcc developers
to deal with.

The main changes are as follows.

We will breakdown the changes into individual patches, as far as possible,
instead of batching changes together.

Each change is accompanied by a much more detailed explanation of what
was changed and why, and the general background of the patch. That
explanation will be sent to gcc-patches.

Although I will do the actual checkins, I will include the primary author
of the patch in the cc list. That way, if anyone has questions, they can
involve the original author in the discussion. I think this will satisfy
the intent of having people check in their own changes, while still
ensuring that appropriate procedures are followed. Every change will be
approved by one of the Ada maintainers before it is checked in.

We are making a much bigger effort to generate shareable small test programs.
There may be some cases where we can't do that, and if so we will identify
these cases, and explain the problem in generating a test program.

We think this approach will allow the Ada changes to be much more digestible
for the gcc community. We believe that having Ada in the GCC tree has some
real value for the gcc community in general (and not just the Ada users)
because the Ada front end exercises some parts of the middle and back end
more strongly than other front-ends, which allows the detection of bugs
earlier than would otherwise be the case.

Arno