gcc 4.3.2 libgcc_s.so exception handling broken?

xorquewasp at googlemail.com xorquewasp at googlemail.com
Sun Jan 18 01:57:53 PST 2009


On 2009-01-18 01:38:12, Garrett Cooper wrote:
> 
> I'd check the release notes between 4.2.x and 4.3.x, and see whether
> or not they invalidated a certain lexigraphical part of C++ that was a
> gray area, which could be affecting your compilation. Have you
> possibly discussed this very issue on the gcc lists yet?

Hello.

Just want to clarify that the C++ example I just gave was because someone
specifically asked for it. I don't think the problem is specific to a
language (and I'm not even using C++) as gcc exception handling is
language independent. Right now, I'm assuming that this is a bug that's
turned up in (at least) 4.3.2 on FreeBSD (works on Debian).

I haven't gone to the gcc lists yet because it seems like this problem
only happens on FreeBSD. They're for later...

> 
> Also, what CFLAGS / CXXFLAGS / CPUTYPE are you using?
> 

Exactly what was shown above plus -O switches -

For C:

  -fexceptions -O2 -g -W -Werror -Wall -std=c99 -pedantic-errors -Wno-unused-parameter

For Ada:

  -O3 -g -fstack-check -gnatwaleFG -gnatVa -gnato -gnata

thanks,
xw


More information about the freebsd-hackers mailing list