This is the mail archive of the
mailing list for the GCC project.
Re: Fix simulator needs_status_wrapper/testglue usage without dejagnu-1.4.4 patches
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Richard dot Earnshaw at buzzard dot freeserve dot co dot uk
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 6 Oct 2004 19:09:19 -0400 (EDT)
- Subject: Re: Fix simulator needs_status_wrapper/testglue usage without dejagnu-1.4.4 patches
- References: <200410062244.i96MiKQx027955@merlin.buzzard.freeserve.co.uk>
On Wed, 6 Oct 2004, Richard Earnshaw wrote:
> This patch:
> * testsuite/lib/libstdc++.exp: Use gcc wrapper.exp and call
> libstdc++_maybe_build_wrapper instead of using local code.
> * lib/gcc-defs.exp: Load wrapper.exp.
> * lib/g++.exp (g++_init): Call g++_maybe_build_wrapper instead of
> using local code.
> * lib/gcc.exp (gcc_init): Similar.
> * lib/gfortran.exp (gfortran_init): Similar.
> * lib/objc.exp (objc_init): Similar.
> * lib/treelang.exp (treelang_init): Similar.
> * lib/wrapper.exp: New file with build_wrapper call machinery in
> Well, specifically the libstdc++ bit is causing all Thumb multilib
> variants of arm-elf to fail.
Things worked with exactly only this patch reversed, no other
changes to the system?
> The problem is that the testglue file isn't
> being rebuilt with the correct options for the multilib under test. For
> some reason this only happens with libstdc++ and not with gcc or g++
> tests, but the failure mode is that all tests spin until they time out and
> it's making testing impossible for me.
Sorry, browsing the patch, I don't see how your analysis could
be correct: you lost me. Compare the old libstdc++.exp wrapper
with what's in the new wrapper.exp. Neither does the kind of
target-specific option business that could cause this mismatch:
they're equal except that wrapper.exp saves options, adds -w and
restores options around the wrapper call. Are you sure it's not
something unrelated to this patch; broken before as well?