------- Additional Comments From wilson at tuliptree dot org 2004-10-29 22:00 -------
Subject: Re: bad unwind info due to multiple returns
(missing epilogue)
On Thu, 2004-10-28 at 02:24, davidm at hpl dot hp dot com wrote:
> # of unexpected failures 115
This is a lot more failures than we should have. I didn't have any luck
in reproducing this though. I did an apt-get update and dist-upgrade on
my debian/unstable partition, rebooted just in case, built and installed
libunwind-0.98 from source, then did a gcc bootstrap and make check, and
got 46 gcc failures. This is from gcc mainline, last updated on Monday.
I am a novice at configuring a debian/unstable system. So maybe I
missed something. I noticed that my debian/unstable partition is using
a 2.4.17 kernel which is apparently the same as debian/testing which
seems a little surprising. I didn't try looking for a debian/unstable
libunwind package. Maybe I need to use that one instead of one I built
myself?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18010
