Hi Michael,
A new bug triaging question.
https://bugs.launchpad.net/ubuntu/+source/ppl/+bug/941676
This one is special too because the failure is on powerpc. This means, I cannot reproduce it easily, and scan through the toolchains (without building).
Matthias has given some information and a guess of what is failing. My idea was to just summarize this, and let the person who takes on the bug make the powerpc investigation.
How do we handle bugs on other architectures in general?
Best regards Åsa
On Thu, Mar 8, 2012 at 3:17 AM, Asa Sandahl asa.sandahl@linaro.org wrote:
Hi Michael,
A new bug triaging question.
https://bugs.launchpad.net/ubuntu/+source/ppl/+bug/941676
This one is special too because the failure is on powerpc. This means, I cannot reproduce it easily, and scan through the toolchains (without building).
Matthias has given some information and a guess of what is failing. My idea was to just summarize this, and let the person who takes on the bug make the powerpc investigation.
How do we handle bugs on other architectures in general?
It's tricky. Most faults are ICEs and can be exercised via a cross compiler built using crosstool-NG or home grown methods. This one is excessive memory usage and should show in a cross build.
Past that you can use inspection or, if all else fails, Canonical have some PowerPC porter boxes that we can get access to.
It wouldn't hurt to see if the same problem exists on ARM - take the file and see if it compiles.
-- Michael
linaro-toolchain@lists.linaro.org