This is the mail archive of the
mailing list for the GCC project.
Re: True "no-exceptions" mode?
- From: Daniel Gutson <daniel dot gutson at tallertechnologies dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Sun, 18 May 2014 16:12:29 -0300
- Subject: Re: True "no-exceptions" mode?
- Authentication-results: sourceware.org; auth=none
- References: <CAF5HaEXwtrW7vS9XELVmEZ1GWmN_=RiM9TAzJSXGRbREA=LCUA at mail dot gmail dot com> <CAH6eHdT5t7KLoDmMfFB=pX3yzMoh=3tgotg79Ku-MJ-tg0XNPQ at mail dot gmail dot com>
On Sun, May 18, 2014 at 1:12 PM, Jonathan Wakely <firstname.lastname@example.org> wrote:
> Sounds like a coding standard not a compiler multilib target.
> If you don't want exceptions don't use them.
If the STL is compiled with exceptions support, I can't get rid
off its overhead. It's not just about not using them, but to
not pay for its overhead (e.g. see newlib).
The 0-overhead principle is violated in this case,
I'm paying for something I don't use in terms of RAM and cost in
HRT applications. That hurts when developing for small-featured
However, there could be two builds of the STL, one with exceptions
support and another much smaller without; a flag like the one I'm proposing
would be useful to select which one to link with in the target fragment file.
Daniel F. Gutson
Chief Engineering Officer, SPD
San Lorenzo 47, 3rd Floor, Office 5
Phone: +54 351 4217888 / +54 351 4218211