public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/14925] libunwind enabled gcc generates incompatible libgcc_s.so.1 Date: Thu, 19 Aug 2004 19:06:00 -0000 [thread overview] Message-ID: <20040819190625.9468.qmail@sourceware.org> (raw) In-Reply-To: <20040412164900.14925.hjl@lucon.org> ------- Additional Comments From hjl at lucon dot org 2004-08-19 19:06 ------- With the patch http://gcc.gnu.org/ml/gcc-patches/2004-08/msg01398.html applied, the ABI-compliant 3rd party libunwind can be used in gcc without causing any binary incompatibility. libunwind 0.98 from David Mosberger is one of such libraries. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14925
next prev parent reply other threads:[~2004-08-19 19:06 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-12 17:21 [Bug target/14925] New: " hjl at lucon dot org 2004-04-12 17:30 ` [Bug target/14925] " pinskia at gcc dot gnu dot org 2004-04-12 22:11 ` hjl at lucon dot org 2004-04-12 23:07 ` hjl at lucon dot org 2004-04-12 23:49 ` mmitchel at gcc dot gnu dot org 2004-05-26 20:36 ` pinskia at gcc dot gnu dot org 2004-07-08 7:50 ` hjl at lucon dot org 2004-07-08 7:52 ` hjl at lucon dot org 2004-07-08 7:59 ` pinskia at gcc dot gnu dot org 2004-07-08 15:13 ` hjl at lucon dot org 2004-07-08 15:47 ` schwab at suse dot de 2004-08-15 3:56 ` pinskia at gcc dot gnu dot org 2004-08-19 19:03 ` hjl at lucon dot org 2004-08-19 19:06 ` hjl at lucon dot org [this message] 2004-08-24 16:14 ` hjl at lucon dot org 2004-08-24 16:15 ` hjl at lucon dot org 2004-08-24 16:16 ` pinskia at gcc dot gnu dot org 2004-08-31 5:29 ` pinskia at gcc dot gnu dot org 2004-09-04 0:16 ` cvs-commit at gcc dot gnu dot org 2004-09-08 15:16 ` cvs-commit at gcc dot gnu dot org
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=20040819190625.9468.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).