On 15/07/10 09:59, Yao Qi wrote:
- How to do tests to these patches. We should apply each of these
patches to gcc.gnu.org/svn/gcc/branches/gcc-4_4-branch, and bootstrap. If this patch is target-specific, shall we build a cross-compiler to test on target board or qemu, or build native compiler on target machine directly? As Loic suggested, in ubuntu, we choose latter approach. Any ARM board that we can access?
Patches are always submitted to the upstream mainline. In this case, what will be GCC 4.6.
In any case, upstream don't accept fixes to release branches unless they fix regressions (i.e. something that used to work in 4.3, but is broken in 4.4), and even then, it normally has to be a backport from mainline.
- How to deal with patches for PR fix, such as pr39429.diff
pr41848.diff pr43323.diff pr40133.diff, etc. We should send updated patches to gcc-patches. Shall we update gcc bugzilla accordingly? say "latest patch is posted somewhere in gcc-patches"
If we fix something in GCC bugzilla we should update bugzilla. The patch can be posted to either gcc-patches, or to bugzilla directly, although I think the former is preferred. Putting a reference in the bug is entirely appropriate.
- Some patches was discussed before in gcc-patches, shall we start a
new thread on the patch discussion or go on in the old thread.
Start a new one, if the old one is very old, and include a link to the historical discussion.
If the patch is already upstream (albeit not in 4.4), then there's nothing to do. I suspect this it the case for all the prXXXX patches - we just need to update the tracker.
Andrew