public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Alexander Kabaev <kabaev@bellatlantic.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6467: Wrong interactions between sjlj-exceptions and inline functions in GCC 2.95.3 on FreeBSD
Date: Thu, 19 Dec 2002 20:06:00 -0000 [thread overview]
Message-ID: <20021220040603.4434.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/6467; it has been noted by GNATS.
From: Alexander Kabaev <kabaev@bellatlantic.net>
To: ak03@gte.com
Cc: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: c++/6467: Wrong interactions between sjlj-exceptions and inline functions in GCC 2.95.3 on FreeBSD
Date: Thu, 19 Dec 2002 23:04:20 -0500
On Thu, 19 Dec 2002 22:53:14 -0500
Alexander Kabaev <kabaev@bellatlantic.net> wrote:
> These bugs have been dealt with a long time ago. This PR should be
> closed.
Sorry, I need to expand on that little. The problems are still there on
gcc-2.95-branch, but the whole integrate has been rewritten for GCC 3.x,
so they do not happen with recent compiler versions. I submitted this
PRs initially to help people who might still use GCC 2.95.x in
production environment. FreeBSD 4.x users, for example.
Meanwhile FreeBSD has applied these fixes locally, so whether this patch
will ever make it into official FSF repository is irrelevant.
--
Alexander Kabaev
next reply other threads:[~2002-12-20 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 20:06 Alexander Kabaev [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-20 8:04 bangerth
2002-12-19 19:00 bangerth
2002-04-25 21:16 ak03
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=20021220040603.4434.qmail@sources.redhat.com \
--to=kabaev@bellatlantic.net \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).