Date: Sun, 18 Jan 2009 09:57:49 +0000 From: xorquewasp@googlemail.com To: Garrett Cooper <yanefbsd@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: gcc 4.3.2 libgcc_s.so exception handling broken? Message-ID: <20090118095749.GA63288@logik.internal.network> In-Reply-To: <7d6fde3d0901180138y61cf4a8bgc01fd5baa684954b@mail.gmail.com> References: <20090117231404.GB77134@logik.internal.network> <Pine.GSO.4.64.0901172248030.18030@zeno.ucsd.edu> <20090118074057.GB43496@logik.internal.network> <7d6fde3d0901180138y61cf4a8bgc01fd5baa684954b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090118095749.GA63288>