From: Jakob Hasse <jakob.hasse@espressif.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <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 01:43:34 +0000 [thread overview]
Message-ID: <HK0PR04MB25305DF434D26CD846E0EEF4E4C59@HK0PR04MB2530.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <CAH6eHdRM+YPt8iM5t+NTPd4m2pxRAeBs2GTuyRR0ehCODUs2jQ@mail.gmail.com>
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?
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"?
Thanks,
Jakob
________________________________
From: Jonathan Wakely <jwakely.gcc@gmail.com>
Sent: Friday, May 6, 2022 4:19 AM
To: Jakob Hasse <jakob.hasse@espressif.com>
Cc: libstdc++@gcc.gnu.org <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]
[External: This email originated outside Espressif]
On Wed, 4 May 2022 at 12:14, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
> On Tue, 3 May 2022 at 11:57, Jakob Hasse via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
> > Number of unexpected failures went down by one and the number of unsupported tests went up by one. 17_intro/headers/c++1998/49745.cc suddenly passes, 22_locale/time_get/get_date/wchar_t/4.cc is suddenly unsupported. I don't know why.
>
> I don't understand that either. I'll try to reproduce that.
I have no idea why you're seeing that, but I have pushed a change to
the master branch that fixes most of the test failures when using
-fno-rtti.
next prev parent reply other threads:[~2022-05-06 1:43 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 [this message]
2022-05-06 6:55 ` Jonathan Wakely
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=HK0PR04MB25305DF434D26CD846E0EEF4E4C59@HK0PR04MB2530.apcprd04.prod.outlook.com \
--to=jakob.hasse@espressif.com \
--cc=ivan@espressif.com \
--cc=jwakely.gcc@gmail.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).