a8e02a00a0
This allows std::make_exception_ptr to be used in a translation unit compiled with -fno-exceptions. This works because the new implementation added for PR 68297 doesn't need to throw or catch anything. The catch is there to handle exceptions from the constructor of the exception object, which we can assume won't happen in a -fno-exceptions TU and so use the __catch macro instead. If the constructor does throw (because it's defined in a different TU which was compiled with exceptions enabled) then that exception will propagate to the make_exception_ptr caller. That seems acceptable for a program that is trying to mix & match TUs compiled with and without exceptions, and using types that throw when constructed. That should be rare, and can't reasonably be expected to have sensible behaviour. This also enables the new implementation for targets that use a non-standard calling convention for the exceptionDestructor callback (specifically, mingw, which uses __thiscall). All we need to do is mark the __dest_thunk function template with the right calling convention. Finally, the useless no-op definition of make_exception_ptr (which is only used if both RTTI and exceptions are disabled) is marked always_inline, to ensure that the linker won't keep that definition and discard the functional ones when both definitions of the function are present in the link. An alternative would be to add the abi_tag attribute to the useless definition, but making it always_inline should work, and it's small enough to always be inlined reliably. libstdc++-v3/ChangeLog: PR libstdc++/85813 * libsupc++/exception_ptr.h (__dest_thunk): Add macro for destructor calling convention. (make_exception_ptr): Enable non-throwing implementation for -fno-exceptions and for non-standard calling conventions. Use always_inline attribute on the useless no-rtti no-exceptions definition. * testsuite/18_support/exception_ptr/64241.cc: Add -fno-rtti so the no-op implementation is still used. |
||
|---|---|---|
| c++tools | ||
| config | ||
| contrib | ||
| fixincludes | ||
| gcc | ||
| gnattools | ||
| gotools | ||
| include | ||
| INSTALL | ||
| intl | ||
| libada | ||
| libatomic | ||
| libbacktrace | ||
| libcc1 | ||
| libcody | ||
| libcpp | ||
| libdecnumber | ||
| libffi | ||
| libgcc | ||
| libgfortran | ||
| libgo | ||
| libgomp | ||
| libiberty | ||
| libitm | ||
| libobjc | ||
| liboffloadmic | ||
| libphobos | ||
| libquadmath | ||
| libsanitizer | ||
| libssp | ||
| libstdc++-v3 | ||
| libvtv | ||
| lto-plugin | ||
| maintainer-scripts | ||
| zlib | ||
| .dir-locals.el | ||
| .gitattributes | ||
| .gitignore | ||
| ABOUT-NLS | ||
| ar-lib | ||
| ChangeLog | ||
| ChangeLog.jit | ||
| ChangeLog.tree-ssa | ||
| compile | ||
| config-ml.in | ||
| config.guess | ||
| config.rpath | ||
| config.sub | ||
| configure | ||
| configure.ac | ||
| COPYING | ||
| COPYING3 | ||
| COPYING3.LIB | ||
| COPYING.LIB | ||
| COPYING.RUNTIME | ||
| depcomp | ||
| install-sh | ||
| libtool-ldflags | ||
| libtool.m4 | ||
| lt~obsolete.m4 | ||
| ltgcc.m4 | ||
| ltmain.sh | ||
| ltoptions.m4 | ||
| ltsugar.m4 | ||
| ltversion.m4 | ||
| MAINTAINERS | ||
| Makefile.def | ||
| Makefile.in | ||
| Makefile.tpl | ||
| missing | ||
| mkdep | ||
| mkinstalldirs | ||
| move-if-change | ||
| multilib.am | ||
| README | ||
| symlink-tree | ||
| test-driver | ||
| ylwrap | ||
This directory contains the GNU Compiler Collection (GCC). The GNU Compiler Collection is free software. See the files whose names start with COPYING for copying permission. The manuals, and some of the runtime libraries, are under different terms; see the individual source files for details. The directory INSTALL contains copies of the installation information as HTML and plain text. The source of this information is gcc/doc/install.texi. The installation information includes details of what is included in the GCC sources and what files GCC installs. See the file gcc/doc/gcc.texi (together with other files that it includes) for usage and porting information. An online readable version of the manual is in the files gcc/doc/gcc.info*. See http://gcc.gnu.org/bugs/ for how to report bugs usefully. Copyright years on GCC source files may be listed using range notation, e.g., 1987-2012, indicating that every year in the range, inclusive, is a copyrightable year that could otherwise be listed individually.