public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: Shlom Marom <devshlom@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Exception handling on AIX5.3 with gcc 3.4.6
Date: Thu, 20 Mar 2008 16:36:00 -0000	[thread overview]
Message-ID: <47E29267.AAFEF6F1@dessent.net> (raw)
In-Reply-To: <c8cc0fd10803200828h393a87ecl5c69f4d5c80375c5@mail.gmail.com>

[ Don't CC: a million different @gcc.gnu.org lists, the whole point of
having them separate is so that people's mailboxes aren't flooded with
mails, which you render ineffective by sending a copy to every list. 
gcc@ especially is about development of gcc not help using it. ]

Shlom Marom wrote:

> If I compiled the program with shared lib-gcc and with the pthread
> libstdc++ - everything works fine and also the base exception is being
> caught as it should.
> ...
> Shared linking: gcc -o tester_shared main.cpp -pthread -I.
> -shared-libgcc -L/usr/lib -ldl -lpthread -lstdc++
> Static linking: gcc -o tester_static main.cpp -L/usr/lib/threads
> -pthread -I. -static-libgcc -L/usr/lib -ldl -lpthread `gcc

A shared libgcc is pretty much required for proper exception handling, I
just don't think you're going to be able to get around that.  This
should hold true for pretty much every target so the fact that it works
with static libgcc on Linux is by accident, or perhaps luck.

Brian

  reply	other threads:[~2008-03-20 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 15:28 Shlom Marom
2008-03-20 16:36 ` Brian Dessent [this message]
2008-03-21 23:36   ` Shlom Marom
2008-03-22  3:26     ` Brian Dessent
2008-03-23  9:22       ` Shlom Marom
2008-03-26  1:26   ` Ian Lance Taylor
2008-03-20 17:23 ` David Edelsohn

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=47E29267.AAFEF6F1@dessent.net \
    --to=brian@dessent.net \
    --cc=devshlom@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).