public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davidm at hpl dot hp dot com" <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: Thu, 21 Oct 2004 18:03:00 -0000	[thread overview]
Message-ID: <20041021180341.18843.qmail@sourceware.org> (raw)
In-Reply-To: <20041015111408.18010.davidm@hpl.hp.com>


------- Additional Comments From davidm at hpl dot hp dot com  2004-10-21 18:03 -------
OK, I tried this patch on the CVS gcc-3_4_branch (the 4.0 branch didn't work at
all for me, even in it's pristine version).  As you said, the patch does fix the
bug I reported.  In addition, the test-suites report the following:

gcc Summary: 4 additional tests now pass (24083, up from 24079)
g++ Summary: 2 new unexpected failures (up from 0).
g77 Summary: no changes
objc Summary: no changes
libstdc++ Summary: no changes
libjava Summary: no changes

I'm not sure the g++ failures are real: if I try and cut & past one of the
failing commands myself, it works just fine.  For example, one of the failures is:

Executing on host: /home/davidm/src/gcc-build-p2/gcc/testsuite/../g++
-B/home/davidm/src/gcc-build-p2/gcc/testsuite/../
/r/wailua/usr/src/misc/gcc-3.4-p2/gcc/testsuite/g++.dg/template/access8.C 
-nostdinc++
-I/home/davidm/src/gcc-build-p2/ia64-unknown-linux-gnu/libstdc++-v3/include/ia64-unknown-linux-gnu
-I/home/davidm/src/gcc-build-p2/ia64-unknown-linux-gnu/libstdc++-v3/include
-I/r/wailua/usr/src/misc/gcc-3.4-p2/libstdc++-v3/libsupc++
-I/r/wailua/usr/src/misc/gcc-3.4-p2/libstdc++-v3/libsupc++
-I/r/wailua/usr/src/misc/gcc-3.4-p2/libstdc++-v3/include/backward
-I/r/wailua/usr/src/misc/gcc-3.4-p2/libstdc++-v3/testsuite -fmessage-length=0  
-ansi -pedantic-errors -Wno-long-long  -S  -o access8.s
WARNING: program timed out.
compiler exited with status 1
FAIL: g++.dg/template/access8.C (test for excess errors)

but when I run this by hand, it works just fine.

I'll see if I can figure out what's going on here tomorrow.


-- 


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


  parent reply	other threads:[~2004-10-21 18:03 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 [this message]
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
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=20041021180341.18843.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).