public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Danny Smith" <danny_r_smith_2001@yahoo.co.nz>
To: cygwin@cygwin.com
Subject: Re: Available for testing: gcc-3.3.1-1 and gcc-mingw-20030911-1
Date: Sat, 13 Sep 2003 20:59:00 -0000	[thread overview]
Message-ID: <20030913205923.16182.qmail@web21403.mail.yahoo.com> (raw)

On Sat, Sep 13, 2003 at 12:43:38PM -0400, Rolf Campbell wrote:
>Christopher Faylor wrote:
>
>>On Sat, Sep 13, 2003 at 12:20:39PM -0400, Rolf Campbell wrote:
>>
>>>Is this new gcc supposed to be ABI compatible with 3.2.x?  Because I 
>>>can't link in libraries compiled with an older version of cygwin g++.
>>>
>>>/c/temp/cppunit-1.8.0/src/cppunit/TestSucessListener.cpp: undefined 
>>>reference to `___gxx_personality_v0'
>>>/c/temp/cppunit-1.8.0/src/cppunit/../../include/cppunit/TestListener.h:33: 
>>>undefined reference to `__Unwind_Resume'
>>
>>Apparently not.
>>
>Ok, let me rephrase:  Do you consider this a problem worth fixing?


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
-fomit-frame-pointer).

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.

Danny

http://search.yahoo.com.au - Yahoo! Search
- Looking for more? Try the new Yahoo! Search

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2003-09-13 20:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-13 20:59 Danny Smith [this message]
2003-09-13 23:07 ` Rolf Campbell
2003-09-14  6:42   ` Gerrit P. Haase
2003-09-14  5:16 ` Charles Wilson
2003-09-14  8:14   ` Danny Smith
2003-09-14  8:35     ` Charles Wilson
  -- strict thread matches above, loose matches on Subject: below --
2003-09-20 19:06 serge
2003-09-20 19:33 ` Christopher Faylor
2003-09-13  0:27 Christopher Faylor
2003-09-13  9:30 ` Max Bowsher
2003-09-13 16:20 ` Rolf Campbell
2003-09-13 16:31   ` Christopher Faylor
2003-09-13 16:43     ` Rolf Campbell
2003-09-13 17:03       ` Christopher Faylor
2003-09-13 18:52   ` Charles Wilson
2003-09-13 19:00     ` Rolf Campbell
2003-09-17  7:05 ` Gerrit P. Haase
2003-09-17 15:26   ` Christopher Faylor
2003-09-17 15:50     ` Gerrit P. Haase
2003-09-17 21:35       ` Christopher Faylor
2003-09-18  7:52         ` Gerrit P. Haase
2003-09-20  9:48     ` Gerrit P. Haase
2003-09-20 18:38       ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030913205923.16182.qmail@web21403.mail.yahoo.com \
    --to=danny_r_smith_2001@yahoo.co.nz \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).