This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PR 3591, PR 5676 - mcore C++
- From: Joe Buck <Joe dot Buck at synopsys dot com>
- To: phil at jaj dot com (Phil Edwards)
- Cc: nickc at cambridge dot redhat dot com (Nick Clifton),jakub at redhat dot com (Jakub Jelinek), gcc at gcc dot gnu dot org
- Date: Fri, 22 Mar 2002 09:07:54 -0800 (PST)
- Subject: Re: PR 3591, PR 5676 - mcore C++
> > > /* The EPOC C++ environment does not support exceptions. */
> > > #define CC1_SPEC "-funsigned-bitfields %{!DIN_GCC:-fno-rtti} %{!DIN_GCC:-fno-exceptions}"
> [...]
> > + # The EPOC C++ environment does not support exceptions,
> > + # and these are required in order to build libstdc++-v3.
Phil Edwards writes:
> Well, that's not exactly true. The libstdc++-v3 code has been carefully
> crafted to support building with -fno-exceptions. Take a look at v3's
> docs/html/configopts.html (I forget the equivalent onelinedocs URL) and
> try configuring with
>
> --enable-cxx-flags='-fno-exceptions'
>
> This doesn't get a whole lot of testing, so it may be broken now.
If this is the case, then it seems that for an embedded target that
does not support exceptions such as EPOC, this flag should be the
default.