* libstdc++ library choices and -fno-exceptions
@ 2010-02-09 20:32 Rob Emanuele
2010-02-10 3:54 ` Ian Lance Taylor
0 siblings, 1 reply; 2+ messages in thread
From: Rob Emanuele @ 2010-02-09 20:32 UTC (permalink / raw)
To: gcc-help
Greetings,
I am writing embedded code for ARM Cortex-M3 processors. In some
cases for a tiny processor we have some c++ code we would like to run
on the Cortex with exceptions disabled. In other cases we would like
to leave them enabled. Is there a way to configure and build g++ so
when it is run with -fno-exceptions it links against a libstdc++ that
is built with -fno-exceptions?
Thanks,
Rob
--
Robert Emanuele
Crystalfontz America, Inc.
www.crystalfontz.com
rje@crystalfontz.com
+1 509 892 1200
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: libstdc++ library choices and -fno-exceptions
2010-02-09 20:32 libstdc++ library choices and -fno-exceptions Rob Emanuele
@ 2010-02-10 3:54 ` Ian Lance Taylor
0 siblings, 0 replies; 2+ messages in thread
From: Ian Lance Taylor @ 2010-02-10 3:54 UTC (permalink / raw)
To: Rob Emanuele; +Cc: gcc-help
Rob Emanuele <rje@crystalfontz.com> writes:
> I am writing embedded code for ARM Cortex-M3 processors. In some
> cases for a tiny processor we have some c++ code we would like to run
> on the Cortex with exceptions disabled. In other cases we would like
> to leave them enabled. Is there a way to configure and build g++ so
> when it is run with -fno-exceptions it links against a libstdc++ that
> is built with -fno-exceptions?
It is possible but you have to do a bit of gcc source hackery and
rebuild gcc. You can treat -fno-exceptions as a multilib. See
http://gcc.gnu.org/onlinedocs/gccint/Target-Fragment.html .
Ian
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-02-10 1:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-02-09 20:32 libstdc++ library choices and -fno-exceptions Rob Emanuele
2010-02-10 3:54 ` Ian Lance Taylor
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).