From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jakob Hasse <jakob.hasse@espressif.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
Rocha Euripedes <rocha.euripedes@espressif.com>,
Ivan Grokhotkov <ivan@espressif.com>
Subject: Re: [PATCH] libstdc++: fix pointer type exception catch [PR105387]
Date: Fri, 6 May 2022 07:55:28 +0100 [thread overview]
Message-ID: <CAH6eHdSZwKPJOB8Wu1z2XkcYqMc9DUO-5we+p7DwMRBo4TKYpA@mail.gmail.com> (raw)
In-Reply-To: <HK0PR04MB25305DF434D26CD846E0EEF4E4C59@HK0PR04MB2530.apcprd04.prod.outlook.com>
On Fri, 6 May 2022, 02:43 Jakob Hasse, <jakob.hasse@espressif.com> wrote:
> I'll re-run tests on current master.
>
> About the pointer-to-member issue: You're right, I missed that. I don't
> know a solution so far. Should I continue preparing the patch anyway, as a
> temporary solution?
>
Yes, please do. I think losing the ability to catch pointers to member via
qualification conversions might be a necessary consequence of avoiding
undefined behaviour and crashes in other cases. It only affects people
building libstdc++ without RTTI anyway, which is unusual.
> If so, I'll adjust the patch according to the comments earlier
> (formalities, coding rules, etc.).
>
> Does GCC's libstdc++-v3 have some kind of "errata"?
>
No, bugzilla serves that purpose, or the release notes for larger changes.
doc/xml/manual/evolution.xml documents user-visible API changes, but this
doesn't qualify, it's just a bug fix.
doc/xml/manual/intro.xml documents implemented defects fixed in the C++
standard itself.
prev parent reply other threads:[~2022-05-06 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 10:56 Jakob Hasse
2022-05-04 11:14 ` Jonathan Wakely
2022-05-04 11:18 ` Jonathan Wakely
2022-05-04 22:47 ` Jonathan Wakely
2022-05-05 20:19 ` Jonathan Wakely
2022-05-06 1:43 ` Jakob Hasse
2022-05-06 6:55 ` Jonathan Wakely [this message]
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=CAH6eHdSZwKPJOB8Wu1z2XkcYqMc9DUO-5we+p7DwMRBo4TKYpA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=ivan@espressif.com \
--cc=jakob.hasse@espressif.com \
--cc=libstdc++@gcc.gnu.org \
--cc=rocha.euripedes@espressif.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).