From: Jeff Law <law@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [wwwdocs] Document libstdc++ header dependency changes
Date: Tue, 1 Dec 2020 15:06:22 -0700 [thread overview]
Message-ID: <36659e07-8e23-2d41-cee7-f06614a4ac6b@redhat.com> (raw)
In-Reply-To: <c7a0df26-4f1d-e14c-3ec5-4a7ca12e1429@pfeifer.com>
On 12/1/20 2:58 PM, Gerald Pfeifer wrote:
> On Thu, 26 Nov 2020, Jonathan Wakely via Gcc-patches wrote:
>>> Also explain how to replace dynamic exception specifications.
>> And a small correction.
> Ah, I was going to point that out. :-)
>
> Let's see how many ports/packages the header cleanup is going to break
> this time. Updating the default version of GCC in FreeBSD has proven a
> painful endeavour the last few times (though the GCC 10 update is mostly
> delayed due to stricter behavior on the Fortran side).
I've already fixed ~100 in Fedora... Those fixes are slowly trickling
to the appropriate upstreams.
Jeff
prev parent reply other threads:[~2020-12-01 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 11:33 Jonathan Wakely
2020-11-26 11:53 ` Jonathan Wakely
2020-12-01 21:58 ` Gerald Pfeifer
2020-12-01 22:06 ` Jeff Law [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=36659e07-8e23-2d41-cee7-f06614a4ac6b@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=libstdc++@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).