Bug 39649 - libstdc++-v3/src/functexcept.cc:65 internal compiler error: verify_eh_tree failed in stage3
Summary: libstdc++-v3/src/functexcept.cc:65 internal compiler error: verify_eh_tree fa...
Status: RESOLVED DUPLICATE of bug 39659
Alias: None
Product: gcc
Classification: Unclassified
Component: libstdc++ (show other bugs)
Version: 4.4.0
: P3 critical
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-05 14:03 UTC by Henrik Nilsson
Modified: 2009-04-06 09:11 UTC (History)
3 users (show)

See Also:
Host: x86_64-unknown-linux-gnu
Target: x86_64-unknown-linux-gnu
Build: x86_64-unknown-linux-gnu
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henrik Nilsson 2009-04-05 14:03:48 UTC
The full error message is:
../../../../libstdc++-v3/src/functexcept.cc: In function ‘void std::__throw_logic_error(const char*)’:
../../../../libstdc++-v3/src/functexcept.cc:65: error: region 6 may contain throw and is contained in region that may not
Eh tree:
   8 must_not_throw also known as:4, 5
     6 allowed_exceptions tree_label:<L3>filter :0 types:
   1 cleanup tree_label:<L9>
     7 allowed_exceptions tree_label:<L7>filter :0 types:
     2 cleanup tree_label:<L2>
       3 cleanup tree_label:<L0>
../../../../libstdc++-v3/src/functexcept.cc:65: internal compiler error: verify_eh_tree failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Using svn revision 145559 of gcc on Fedora 8
x86_64 AMD Phenom 9850 CPU
gcc configured with ../configure --prefix=/home/rakhun/systembuilder/GNU-Linux/usr --with-gmp=/home/rakhun/systembuilder/GNU-Linux/usr --with-mpfr=/home/rakhun/systembuilder/GNU-Linux/usr --enable-languages=c,c++ --disable-werror
and compile initiated with 'make'

Log of make output: http://ei87.org/~rakhun/gccerrors.log
functexcept.ii: http://ei87.org/~rakhun/functexcept.ii (not sure if it is relevant or not)
Comment 1 Richard Biener 2009-04-06 09:11:53 UTC

*** This bug has been marked as a duplicate of 39659 ***