On 12/16/2015 03:46 AM, Jan-Benedict Glaw wrote:
On Tue, 2015-12-15 10:43:58 -0700, Jeff Law <l...@redhat.com> wrote:
On 12/14/2015 01:07 PM, Jan-Benedict Glaw wrote:
On Mon, 2015-12-14 18:54:28 +0000, Moore, Catherine
<catherine_mo...@mentor.com> wrote:
avr-rtems
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478544
mipsel-elf
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478844
mipsisa64r2-sde-elf
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478855
mipsisa64sb1-elf
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478865
mips-rtems
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478877
powerpc-eabialtivec
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478922
powerpc-eabispe
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478932
powerpc-rtems
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478956
ppc-elf
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478968
sh-superh-elf
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=479077
Is there an easy way to reproduce the MIPS problems that you
reported? I don't seem to be able to do it with a cross-compiler
targeting mipsel-elf.
What's your build compiler? For these builds, where it showed up, I'm
using a freshly compiles HEAD/master version. So basically, compile a
current GCC for your build machine:
Right. This is something that only shows up when using the trunk to build
the crosses.
When I looked, I thought I bisected it to the delayed folding work.
Shall I bisect one of the cases anew, with the "Test value of
_GLIBCXX_USE_C99_WCHAR not whether it is defined" patch that uncovered
it, applied? Starting with some arbitrary old revision?
Yes. I'd really like to see config-list.mk working again. The first
step is always building a test the developers can easily work with.
jeff
