This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC 4.3.0 Status Report (2007-06-07)


Michael Meissner wrote:

> I think a gradual approach is the right way.  I think this can be done in the
> stage 2 time frame, but it could be pushed to gcc 4.4 (but we will have the
> same problem as we have now).  The way I see it, the steps would be:
> 
> 1) Add the basic infrastructure, iterator macros, stdarg_p, prototype_p,
>    etc. to the tree.
> 
> 2) Change the back ends, 1 by 1 to use the new infrastructure support.
> 
> 3) Change the front ends, 1 by 1 to use the new infrastructure support.
> 
> 4) Remove/rename TYPE_ARG_TYPES, and fix any random breakage.
> 
> 5) Switch the infrastructure underneath to use vectors.
> 
> Until #4, you are only changing one thing at a time, and can easily verify that
> the change works.

Yes, I think that this is a good plan.  We can evaluate whether #4 has
to happen on a branch and wait for 4.4 when we get to it.  But, 1, 2, 3
I think are non-controversial, and can go into mainline in real time,
which is nice.

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]