From: Tom Honermann <tom@honermann.net>
To: gcc@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Cc: Jason Merrill <jason@redhat.com>
Subject: Re: GCC 9.2 Status Report (2019-08-05), branch frozen for release
Date: Thu, 08 Aug 2019 14:49:00 -0000 [thread overview]
Message-ID: <7458f464-083e-02c1-4430-16c3871a89fb@honermann.net> (raw)
> Status
> ======
>
> The first 9.2 release candidate has been released.
> The GCC 9 branch is frozen for preparation of the GCC 9.2 release.
> All changes to the branch now require release manager approval.
Hi, Jakub. If at all possible, I'd like to request that a back port of
PR c++/88095 [1] be included in the gcc 9.2 release.
The rationale for including this is that it is required for one of the
approaches discussed in P1423 [2] (see [3]) that may be useful for some
programmers to mitigate backward compatibility impact from the adoption
of char8_t in C++20 via P0482 [4]. Having this feature working in 9.2
would give impacted programmers more time to evaluate their C++20
migration options.
The patch has already been integrated in trunk [5]. I verified that it
applies cleanly against the gcc-9-branch (with the exception of the
ChangeLog changes), and that tests complete successfully on Linux
x86_64. There are no target dependencies involved in this change.
Tom.
[1]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88095
[2]: http://wg21.link/p1423
[3]: http://wg21.link/p1423#emulate
[4]: http://wg21.link/p0482
[5]: https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=274123
next reply other threads:[~2019-08-08 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 14:49 Tom Honermann [this message]
2019-08-08 15:04 ` Jakub Jelinek
2019-08-08 15:57 ` Tom Honermann
-- strict thread matches above, loose matches on Subject: below --
2019-08-05 13:22 Jakub Jelinek
2019-08-05 17:03 ` Martin Sebor
2019-08-06 7:17 ` Jakub Jelinek
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=7458f464-083e-02c1-4430-16c3871a89fb@honermann.net \
--to=tom@honermann.net \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.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).