[Bug c++/61611] New: Incorrect exception rethrown from a function-try-catch block when a nested try-catch executes

[bspencer at blackberry dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61611

            Bug ID: 61611
           Summary: Incorrect exception rethrown from a function-try-catch
                    block when a nested try-catch executes
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bspencer at blackberry dot com

Created attachment 33006
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33006&action=edit
Test program demonstrating the issue

In a try-catch (catch) block nested within, but separate from, a
function-try-catch (catch) block, gcc 4.7.2 for Linux (Debian) and gcc 4.8 for
Linux are both incorrectly re-throwing the exception caught inside the nested
catch block as that nested catch block exits.

Attached is a program that shows the error when compiled with -DFUNCTION_TRY

The program prints "PASS" when the correct exception propagates and and "FAIL"
when the incorrect exception propagates.

Note that this does not appear to be the behaviour of

15.3/15: "The currently handled exception is rethrown if control reaches the
end of a handler of the function-try-block of a constructor or destructor."

because the control is not reaching the end of such a handler.  Thus, this
report differs from Bug #45481.

Perhaps _all_ catch blocks (including nested catch blocks) in a constructor
function try-catch are rethrowing when control reaches the end of them instead
of only the catch blocks of the actual constructor function try-catch
structure.

$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.2-5'
--with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs
--enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.7 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object
--enable-plugin --enable-objc-gc --with-arch-32=i586 --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.7.2 (Debian 4.7.2-5)

$ g++ -Wall -o test test.cc
$ ./test
main() starts
Caught out_of_range: out_of_range
Caught length_error: length_error
Re-throw original ex
TOP Caught out_of_range: out_of_range
PASS
main() stops

$ g++ -Wall -o test test.cc -DFUNCTION_TRY
$ ./test
main() starts
Caught out_of_range: out_of_range
Caught length_error: length_error
TOP Caught length_error: length_error
FAIL
main() stops

The attched program passes with clang++ (clang-503.0.40) with or without
-DFUNCTION_TRY.

Apologies for the non-preprocessed test file, but it does use only standard
headers.