public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at tuliptree dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/18010] bad unwind info due to multiple returns (missing epilogue)
Date: Fri, 29 Oct 2004 22:00:00 -0000 [thread overview]
Message-ID: <20041029220016.9724.qmail@sourceware.org> (raw)
In-Reply-To: <20041015111408.18010.davidm@hpl.hp.com>
------- 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
next prev parent reply other threads:[~2004-10-29 22:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 11:14 [Bug target/18010] New: " davidm at hpl dot hp dot com
2004-10-15 11:15 ` [Bug target/18010] " davidm at hpl dot hp dot com
2004-10-19 1:07 ` wilson at specifixinc dot com
2004-10-19 18:08 ` davidm at hpl dot hp dot com
2004-10-21 18:03 ` davidm at hpl dot hp dot com
2004-10-21 18:07 ` pinskia at gcc dot gnu dot org
2004-10-22 10:57 ` davidm at hpl dot hp dot com
2004-10-25 23:54 ` wilson at tuliptree dot org
2004-10-26 0:06 ` wilson at tuliptree dot org
2004-10-26 8:49 ` davidm at hpl dot hp dot com
2004-10-27 1:36 ` cvs-commit at gcc dot gnu dot org
2004-10-27 1:48 ` wilson at gcc dot gnu dot org
2004-10-27 11:05 ` davidm at hpl dot hp dot com
2004-10-27 19:51 ` wilson at tuliptree dot org
2004-10-28 1:16 ` wilson at tuliptree dot org
2004-10-28 9:24 ` davidm at hpl dot hp dot com
2004-10-29 22:00 ` wilson at tuliptree dot org [this message]
2004-11-04 18:07 ` davidm at hpl dot hp dot com
2004-11-24 22:24 ` cvs-commit at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041029220016.9724.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).