Upstream merge progress
yao.qi at linaro.org
Thu Jul 15 09:59:39 BST 2010
Andrew Stubbs wrote:
> Hi All,
> I've created a new wiki page to track our upstream merge process.
> I'll add the new patches (using the script) periodically, for now, but
> maybe it could go on a cron job somewhere in future.
This scrip is great.
Some questions on upstream merge process,
1. 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?
2. 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"
3. 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.
Finally, If there is a reference that ubuntu patch goes to upstreams,
please give me a link, that will be pretty useful for me.
> The idea is that people write useful thing in this page manually, as and
> when state changes. If we don't do something like this, we'll lose track
> of what's submitted, and what isn't.
> linaro-toolchain mailing list
> linaro-toolchain at lists.linaro.org
More information about the linaro-toolchain