This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Available for testing: gcc-3.3.1-1 and gcc-mingw-20030911-1

Danny Smith wrote:

gcc 3.2-3 used Dwarf2 exceptions, which worked most of the time. (In fact,
I don't recall any bug reports at all on cygwin list).  But it didn't work
with w32api callbacks, nor with some combinations of compiler switches
(notably -mcpu=i586 or -mno-accumulate-outgoing-args and

cygwin gcc-3.3.1 uses setjmp-longjmp exception mechanism,
mingw does too and has done since gcc-3.2.1.

The two undefined references are Dwarf2 specific.  The corresponding
SjLj symbols are __gxx_personality_sj0 and  __Unwind_SjLj_Resume.

So, just to make sure I understand...

This "problem" only affects C++ code -- and only C++ code which uses exceptions. If a C++ library uses exceptions, it should be recompiled with the new compiler. If a C++ _program_ uses excetions -- or uses a (C++) library which uses exceptions -- then it should be recompiled/relinked too, but only after the suspect lib has been recompiled with gcc-3.3.1, as well.

But C code (libraries, apps, etc) are unaffected, and need no recompiling.



-- Unsubscribe info: Problem reports: Documentation: FAQ:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]