From: FX Coudert <fxcoudert@gmail.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: Sam James <sam@gentoo.org>, GCC Patches <gcc-patches@gcc.gnu.org>,
dimitry@andric.com
Subject: Re: [PATCH] Include safe-ctype.h after C++ standard headers, to avoid over-poisoning
Date: Wed, 6 Mar 2024 15:57:41 +0100 [thread overview]
Message-ID: <C7DDF058-CB5D-4637-91DE-0BA413471786@gmail.com> (raw)
In-Reply-To: <06E40B8A-8716-4521-BF5D-F3858174268A@sandoe.co.uk>
> Hmm I recall trying it and finding a problem - was there some different fix applied
> in the end?
The bug is still open, I don’t think a patch was applied, and I don’t find any email to the list stating what the problem could be.
FX
next prev parent reply other threads:[~2024-03-06 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 13:42 FX Coudert
2024-03-06 13:54 ` Sam James
2024-03-06 14:35 ` Iain Sandoe
2024-03-06 14:57 ` FX Coudert [this message]
2024-03-06 23:02 ` Dimitry Andric
2024-03-07 7:11 ` Iain Sandoe
2024-03-07 9:51 ` Richard Biener
2024-03-07 13:40 ` FX Coudert
2024-04-03 9:01 ` Iain Sandoe
2024-04-03 9:38 ` Richard Biener
-- strict thread matches above, loose matches on Subject: below --
2023-09-28 16:37 Dimitry Andric
2024-01-30 16:19 ` 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=C7DDF058-CB5D-4637-91DE-0BA413471786@gmail.com \
--to=fxcoudert@gmail.com \
--cc=dimitry@andric.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=sam@gentoo.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).