[PATCH 00/89] Compile-time gimple-checking

[Jeff Law]

On 04/22/14 02:36, Richard Biener wrote:
> On Mon, Apr 21, 2014 at 6:56 PM, David Malcolm <dmalcolm@redhat.com> wrote:
>> This is a greatly-expanded version of:
>>    http://gcc.gnu.org/ml/gcc-patches/2013-12/msg01262.html
>>
>> As of r205034 (de6bd75e3c9bc1efe8a6387d48eedaa4dafe622d) and
>> r205428 (a90353203da18288cdac1b0b78fe7b22c69fe63f) the various gimple
>> statements form a C++ inheritance hierarchy, but we're not yet making much
>> use of that in the code: everything refers to just "gimple" (or
>> "const_gimple"), and type-checking is performed at run-time within the
>> various gimple_foo_* accessors in gimple.h, and almost nowhere else.
>>
>> The following patch series introduces compile-time checking of much of
>> the handling of gimple statements.
>>
>> Various new typedefs are introduced for pointers to statements where the
>> specific code is known, matching the corresponding names from gimple.def.
>
> Even though I like these changes in principle I also wear a release
> managers hat.  Being one of the persons doing frequent backports
> of trunk fixes to branches this will cause a _lot_ of headache.  So ... can
> we delay this until, say, 4.9.1 is out?
Understood.

So how about we proceed with the review & approvals, but they stage in 
after 4.9.1?  Ideally by the time 4.9.1 is ready, the entire series in 
its final form has been reviewed and approved.



jeff