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

[wilson at tuliptree dot org]

------- Additional Comments From wilson at tuliptree dot org  2004-10-28 01:16 -------
Subject: Re:  bad unwind info due to multiple returns
	(missing epilogue)

On Wed, 2004-10-27 at 04:05, davidm at hpl dot hp dot com wrote:
> Command: /home/davidm/src/gcc/gcc/cc1 -quiet -iprefix /home/davidm/src/gcc/gcc/.
> ./lib/gcc/ia64-unknown-linux-gnu/4.0.0/ -isystem /home/davidm/src/gcc/gcc/includ
> e /r/wailua/usr/src/misc/gcc/gcc/testsuite/gcc.c-torture/compile/20001226-1.c -q
> uiet -dumpbase 20001226-1.c -auxbase-strip 20001226-1.o -Os -w -o /tmp/ccR2zJ8h.

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? 
I agree the results should be better, but there is only so much I can do
in the limited time I have available for IA-64 gcc work.  If you think I
should be spending more time looking at gcc testsuite results, I can try
shifting my priorities.  I've mostly been trying to respond to bug
reports, and not worrying about the testsuite results.



-- 


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