[Bug target/18010] bad unwind info due to multiple returns (missing epilogue)

[davidm at hpl dot hp dot com]

------- Additional Comments From davidm at hpl dot hp dot com  2004-10-28 09:24 -------
(In reply to comment #16)
> Perhaps I should have read your message closer.  I get timeouts for this
> testcase also.  However, it bootstraps fine, and the total number of
> unexpected gcc failures is only 45, which is really not that bad when
> you consider that there is no one actively maintaining the IA-64 port. 
> Only 4 of these are timeouts.  Are you seeing worse results than this? 

Yes, it's worse but not nearly as bad as I thought.  If I let the test-suite
complete, I get:

                === gcc Summary ===

# of expected passes            30227
# of unexpected failures        115
# of unexpected successes       3
# of expected failures          82
# of unresolved testcases       52
# of untested testcases         28
# of unsupported tests          498

Perhaps the additional failures are due to the fact that my machine is running
Debian/unstable.  Anyhow, this clearly isn't as bad as I thought.  I saw a
couple of timeouts in a row and since that took quite some time, I thought it
was hopeless.  I should have been more patient.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18010