On Fri, 2005-01-21 at 17:50 +0100, Giovanni Bajo wrote:
Why not putting it on a branch? If you are going to finish and submit it for 4.1, it might be easier to use CVS.
It might also be easier for those of us who want to play with the code, without having to find a suitable sync point between the patch and mainline sources.
I have created a new branch, "reload-branch", on which I'm going to check in these changes. Once I've done that, I'll commit the patch below to mention the branch in the documentation.
Bernd
Index: cvs.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvs.html,v
retrieving revision 1.183
diff -c -p -r1.183 cvs.html
*** cvs.html 14 Mar 2005 22:35:59 -0000 1.183
--- cvs.html 18 Mar 2005 17:20:13 -0000
*************** particular releases or snapshots or the
*** 255,260 ****
--- 255,265 ----
routinely merged with mainline. Patches should be marked with the
tag <code>[dfp]</code> in the subject line.</dd>
+ <dt>reload-branch</dt>
+ <dd>This branch contains a version of reload in which the tracking
+ of reload register lifetimes and the inheritance code has been
+ rewritten in an attempt to make it more maintainable.</dd>
+
</dl>
<h4>Architecture-specific</h4>
