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

2004-11-24 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-11-24 22:23 --- Subject: Bug 18010 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-3_4-rhl-branch Changes by: [EMAIL PROTECTED] 2004-11-24 22:22:29 Modified files: gcc:

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

2004-11-04 Thread davidm at hpl dot hp dot com
--- Additional Comments From davidm at hpl dot hp dot com 2004-11-04 18:06 --- (In reply to comment #18) On Thu, 2004-10-28 at 02:24, davidm at hpl dot hp dot com wrote: # of unexpected failures115 This is a lot more failures than we should have. I didn't have any luck in

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

2004-10-29 Thread wilson at tuliptree dot org
--- 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 failures115 This is a lot more

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

2004-10-28 Thread 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,

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

2004-10-27 Thread davidm at hpl dot hp dot com
--- Additional Comments From davidm at hpl dot hp dot com 2004-10-27 11:04 --- (In reply to comment #11) Subject: Re: bad unwind info due to multiple returns (missing epilogue) On Tue, 2004-10-26 at 01:49, davidm at hpl dot hp dot com wrote: The compiler seemed to get stuck

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

2004-10-27 Thread wilson at tuliptree dot org
--- Additional Comments From wilson at tuliptree dot org 2004-10-27 19:50 --- 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: This was on a Debian/unstable system. How do you run

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

2004-10-27 Thread 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

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

2004-10-26 Thread davidm at hpl dot hp dot com
--- Additional Comments From davidm at hpl dot hp dot com 2004-10-26 08:49 --- (In reply to comment #9) You didn't say what kind of problems you ran into with gcc mainline. The compiler seemed to get stuck in an apparent endless loop. make check quickly resulted in timeout failures

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

2004-10-26 Thread wilson at tuliptree dot org
--- Additional Comments From wilson at tuliptree dot org 2004-10-27 01:29 --- Subject: Re: bad unwind info due to multiple returns (missing epilogue) On Tue, 2004-10-26 at 01:49, davidm at hpl dot hp dot com wrote: The compiler seemed to get stuck in an apparent endless loop.

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

2004-10-26 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-10-27 01:36 --- Subject: Bug 18010 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2004-10-27 01:36:12 Modified files: gcc: ChangeLog emit-rtl.c Log message:

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

2004-10-26 Thread wilson at gcc dot gnu dot org
--- Additional Comments From wilson at gcc dot gnu dot org 2004-10-27 01:48 --- Fixed. -- What|Removed |Added Status|NEW |RESOLVED

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

2004-10-25 Thread wilson at tuliptree dot org
--- Additional Comments From wilson at tuliptree dot org 2004-10-25 23:54 --- Subject: Re: bad unwind info due to multiple returns (missing epilogue) On Fri, 2004-10-22 at 03:57, davidm at hpl dot hp dot com wrote: It looks to me as if expect sometimes fails to notice the

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

2004-10-25 Thread wilson at tuliptree dot org
--- Additional Comments From wilson at tuliptree dot org 2004-10-26 00:06 --- Subject: Re: bad unwind info due to multiple returns (missing epilogue) On Thu, 2004-10-21 at 11:03, davidm at hpl dot hp dot com wrote: OK, I tried this patch on the CVS gcc-3_4_branch (the 4.0

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

2004-10-22 Thread davidm at hpl dot hp dot com
--- Additional Comments From davidm at hpl dot hp dot com 2004-10-22 10:57 --- (In reply to comment #5) Argh, I reran make check-g++ with the original (unpatched) GCC and am now seeing 3 unexpected failures (when the exact same compiler produced 0 failures yesterday). From what I can

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

2004-10-21 Thread davidm at hpl dot hp dot 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

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

2004-10-21 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-21 18:07 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW

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

2004-10-19 Thread davidm at hpl dot hp dot com
--- Additional Comments From davidm at hpl dot hp dot com 2004-10-19 18:08 --- (In reply to comment #2) Subject: Re: New: bad unwind info due to multiple returns (missing epilogue) On Fri, 2004-10-15 at 04:14, davidm at hpl dot hp dot com wrote: To fix this bug, GCC should be

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

2004-10-18 Thread wilson at specifixinc dot com
--- Additional Comments From wilson at specifixinc dot com 2004-10-19 01:07 --- Subject: Re: New: bad unwind info due to multiple returns (missing epilogue) On Fri, 2004-10-15 at 04:14, davidm at hpl dot hp dot com wrote: To fix this bug, GCC should be emitting a .restore sp

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

2004-10-15 Thread davidm at hpl dot hp dot com
--- Additional Comments From davidm at hpl dot hp dot com 2004-10-15 11:15 --- Created an attachment (id=7356) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=7356action=view) test-ptrace-misc.c Test case. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18010