This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Question on _GLIBCXX_HOSTED macro libstdc++ and libsupc++


Hi,

In libstdc++-v3/libsupc++/eh_term_handler.cc, it says by default the
demangler things are pulled in,
according to whether _GLIBCXX_HOSTED is defined. the demangler
exception terminating handler
are really big, especially for embedded system.

Secondly, _GLIBCXX_HOSTED is now defined if --enable-hosted-libstdcxx
is given(by default it is).
This option also controls whether libstdc++.a itself is built for target system.

So, for an embedded system, how could I provide the earlier "silent
death" handler by defining _GLIBCXX_HOSTED,
also with libstdc++ built?

Any suggestion? Thanks in advance.
FYI, all above are talking about cross-toolchain.

-- 
Best Regards.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]