This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/18010] bad unwind info due to multiple returns (missing epilogue)
- From: "davidm at hpl dot hp dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Oct 2004 10:57:34 -0000
- Subject: [Bug target/18010] bad unwind info due to multiple returns (missing epilogue)
- References: <20041015111408.18010.davidm@hpl.hp.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From davidm at hpl dot hp dot com 2004-10-22 10:57 -------
(In reply to comment #5)
Argh, I reran "make check-g++" with the original (unpatched) GCC and am now
seeing 3 unexpected failures (when the exact same compiler produced 0 failures
yesterday). From what I can see, these failures are due to problems in the
test-infrastructure: they all show up as timeouts after a compile. It looks to
me as if "expect" sometimes fails to notice the (failure-free) termination of
the compiler and that leads to subsequent and spurious test-suite failures.
I'll see if this is a bug in "expect".
I wonder if the failure(s) Jim saw for the patch for bug #13158 have the same
root-cause.
Has anyone heard of such spurious failures before?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18010