[Bug d/110471] d: Don't generate code that throws exceptions when compiling with `-fno-exceptions'

["cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Iain Buclaw
<ibuclaw@gcc.gnu.org>:

https://gcc.gnu.org/g:6e7909191ada316a426739eab88139d63194e05a

commit r13-7518-g6e7909191ada316a426739eab88139d63194e05a
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Sat Jul 1 17:01:30 2023 +0200

    d: Don't generate code that throws exceptions when compiling with
`-fno-exceptions'

    The version flags for RTMI, RTTI, and exceptions was unconditionally
    predefined.  These are now only predefined if the feature flag is
    enabled.  It was noticed that there was no `-fexceptions' definition
    inside d/lang.opt, so the detection of the exceptions option flag was
    only partially working.  Once that was fixed, a few places in the
    front-end implementation were found to fall fowl of `nothrow' rules,
    these have been fixed upstream and backported here as well.

    Reviewed-on: https://github.com/dlang/dmd/pull/15357
                 https://github.com/dlang/dmd/pull/15360

            PR d/110471

    gcc/d/ChangeLog:

            * d-builtins.cc (d_init_versions): Predefine D_ModuleInfo,
            D_Exceptions, and D_TypeInfo only if feature is enabled.
            * lang.opt: Add -fexceptions.

    gcc/testsuite/ChangeLog:

            * gdc.dg/pr110471a.d: New test.
            * gdc.dg/pr110471b.d: New test.
            * gdc.dg/pr110471c.d: New test.

    (cherry picked from commit da108c75ad386b3f1f47abb2265296e4b61d578a)