This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/50737] FAIL: Throw_3 -O3 execution, generic dwarf2 EH problem?
- From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 15 Oct 2011 10:57:57 +0000
- Subject: [Bug target/50737] FAIL: Throw_3 -O3 execution, generic dwarf2 EH problem?
- Auto-submitted: auto-generated
- References: <bug-50737-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50737
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot
| |gnu.org
--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-10-15 10:57:57 UTC ---
> IMO, this points to a bug in generic dwarf2 exception handling, in how context
> is identified. For illustration, I will attach asm dump, object dump and
> corresponding .eh_frame --dwarf dump of Throw_3.java.
This is an old debate. This was changed by Geoff in 2007:
http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01252.html
The problematic function is leaf though; how come it appears in the unwind
chain?
Does it raise a signal? If so, there may be a missing _Unwind_IsSignalFrame
bit.