From: Benjamin Kosnik <bkoz@redhat.com>
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: PR 8134: C++ crash
Date: Tue, 15 Oct 2002 12:25:00 -0000 [thread overview]
Message-ID: <20021015134402.7fefd09f.bkoz@redhat.com> (raw)
... as specified, there is only one fix:
> b) Move my changes over.
>
> As far as we know, these are correct -- but they are substantial,
> and therefore risky.
I'm for this.
You can try the 'make check-abi' to see if any library changes are
introduced. This is not especially helpful for this issue, probably.
The other option would be for you to run your C++ ABI testers against
the patched gcc-3_2-branch code, and let us know if it works.
I don't have to feel the holes, mate. I'll believe you if you say it works.
-benjamin
next reply other threads:[~2002-10-15 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 12:25 Benjamin Kosnik [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 4:03 Reichelt
2002-10-15 12:15 Mark Mitchell
2002-10-15 12:37 ` Gabriel Dos Reis
2002-10-15 12:59 ` Nathan Sidwell
2002-10-16 13:02 ` Mark Mitchell
2002-10-16 13:23 ` Nathan Sidwell
2002-10-16 13:24 ` Mark Mitchell
2002-10-15 15:38 ` Jason Merrill
2002-10-15 16:41 ` Mark Mitchell
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=20021015134402.7fefd09f.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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).