Re: no-exceptions and libstdc++ still including unwind code and emergency_buffer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It turned out to be just that.  I re-compiled g++ with libstdc++ and
used the option: --enable-cxx-flags='-fno-exceptions'

That took care of those functions nicely.

Thank you.

On Mon, Jun 29, 2009 at 2:44 PM, Ian Lance Taylor<iant@xxxxxxxxxx> wrote:
> Rob Emanuele <poorarm@xxxxxxxxxxx> writes:
>
>> I'm working with gcc version 4.3.3.  I'm trying to get g++ to compile
>> an arm-eabi binary as stripped down as possible for an embedded
>> platform.
>>
>> Since I'm not using exceptions I am compiling with -fno-exceptions
>> which from a few mailing list posts like this:
>> http://gcc.gnu.org/ml/gcc/2006-11/msg00467.html
>> should keep __gxx_personality_v0 from being included and therefor the
>> unwinding code with the emergency_buffer.
>>
>> This doesn't seem to be the case.  I'm wondering what else I may need
>> to do in order to remove this code?
>
> You may be able to use the linker's -Map option to find out why
> __gxx_personality_v0 is being pulled in.  It may be that you are pulling
> in code from -lstdc++, or some other library, which was compiled with
> exceptions.
>
> Ian
>


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux