On Mon, 5 Dec 2011, Joern Rennecke wrote: > I find that exception handling doesn't work properly for the epiphany with > recent gcc sources (it worked in the pre-merged port with sources from July). > I suppose that is related to the change mentioned in: > http://gcc.gnu.org/ml/gcc-patches/2011-11/msg01926.html > > Looking at the cleanup-5.c failure, I see that _Unwind_ForcedUnwind > calls _Unwind_SjLj_Register, thus we never unwind to where we are supposed > to unwind. > > I can fix this in libgcc/config/epiphany/t-epiphany with: > > unwind-sjlj.o : CFLAGS += -fno-exceptions > unwind-sjlj.o : c_flags := $(filter-out -fexceptions,$(cflags)) > > Is that the right way to do it? Or should we more generally remove > -fexceptions > from the build rules for the exception handling runtime?
It shouldn't be there in the first place, but you don't provide much details on your merge and svn revisions for anyone to compare notes on similar experiences. For example, judging from the date of your message, I should not guess the following, still... This sounds very similar to <http://gcc.gnu.org/ml/gcc-patches/2011-11/msg02001.html> in which -fexceptions was incorrectly applied as you mention. This was fixed with r181544, about Nov 20th. (The problem would be visible on all static-only platforms.) brgds, H-P
